This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-23
Channels
- # arachne (3)
- # aws (1)
- # bangalore-clj (2)
- # beginners (19)
- # boot (151)
- # cider (72)
- # cljs-dev (9)
- # cljsjs (7)
- # cljsrn (37)
- # clojure (215)
- # clojure-austin (1)
- # clojure-denmark (2)
- # clojure-dev (68)
- # clojure-india (1)
- # clojure-ireland (2)
- # clojure-italy (4)
- # clojure-mke (1)
- # clojure-nl (4)
- # clojure-russia (4)
- # clojure-serbia (1)
- # clojure-spec (29)
- # clojure-uk (23)
- # clojurescript (23)
- # cursive (24)
- # datomic (71)
- # emacs (5)
- # events (1)
- # gsoc (11)
- # hoplon (20)
- # klipse (4)
- # lambdaisland (2)
- # leiningen (3)
- # luminus (3)
- # off-topic (30)
- # om (40)
- # om-next (1)
- # onyx (15)
- # pedestal (19)
- # perun (7)
- # planck (23)
- # proton (1)
- # protorepl (2)
- # re-frame (35)
- # reagent (21)
- # ring-swagger (38)
- # rum (19)
- # spacemacs (9)
- # untangled (11)
- # vim (5)
- # yada (4)
getting crazy slow planck startup after upgrading to 2, I'm sure it's not planck itself but something in my environment, but anyone have any ideas how to track down?
@bfabry Try planck -X -d
to see startup timing. Is it lengthy to get the REPL running?
11326-storage:~ bfabry$ planck -X -d
parse opts: 0.001953 0.001953
check cache path: 0.296078 0.298031
init classpath: 0.010753 0.308784
check theme: 0.004087 0.312871
check tty: 0.008288 0.321159
Planck 2.0.0-beta.6
ClojureScript 1.9.397
Docs: (doc function-name-here)
(find-doc "part-of-name-here")
Source: (source function-name-here)
Exit: Control+D or :cljs/quit or exit or quit
Results: Stored in vars *1, *2, *3, an exception in *e
cljs.user=> JS context created: 13.115642 13.436801
goog/deps.js: 41.677061 55.113862
goog/reflect/reflect.js: 62.238267 117.352129
goog/math/long.js: 0.254391 117.606520
*snip*
I'm a bit of an "I'll update OSX when I get a new laptop" guy, OSX upgrades just always seem to go badly
I can see if I can repro. I have access to a VM running that, and a physical box running Mavericks.
maybe I should just try and upgrade... ugh, but it'll definitely kill my env and eat a day
No… 16-second startup is definitely not caused by an older OS. Something really odd is going on IMHO.
I’m getting curl complaining on Yosemite about SSL… gonna see if I can figure that out
@bfabry I failed to repro on Yosemite. I’ve opened a ticket where we can add info https://github.com/mfikes/planck/issues/431
@bfabry It would be interesting to know what timings you are getting near the end of the -X
output. I’m wondering if it is blocking excessively long waiting for the “engine ready” event. Here is what I see:
window global: 0.066482 543.739797
register fns: 0.077711 543.817508
monkey-patch system-time: 0.052222 543.869730
setup command line args: 0.036790 543.906520
setTimeout: 0.078460 543.984980
engine ready: 0.753364 1789.779455
cljs.user=>