This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (8)
- # beginners (99)
- # boot (60)
- # cider (44)
- # cljs-dev (47)
- # cljsrn (68)
- # clojure (223)
- # clojure-art (1)
- # clojure-russia (190)
- # clojure-sg (9)
- # clojure-uk (2)
- # clojurecup (1)
- # clojurescript (59)
- # clojurex (3)
- # core-async (43)
- # core-typed (2)
- # cursive (18)
- # datavis (7)
- # datomic (16)
- # events (2)
- # funcool (3)
- # hoplon (3)
- # jobs (1)
- # lein-figwheel (10)
- # leiningen (6)
- # off-topic (1)
- # om (123)
- # onyx (57)
- # parinfer (16)
- # portland-or (2)
- # random (1)
- # re-frame (4)
- # reagent (7)
- # remote-jobs (1)
- # spacemacs (12)
@martinklepsch and @nberger I've gotten the Collection Check CLJS port up and running. Lean HAMT now passes for 10000 Collection Check tests! Thanks for all your work.
@dnolen: I've gotten the improved iteration up for Lean HAMT, it's
25% - 50% faster for v8 and 100% slower in SpiderMonkey.
Nope, I've had trouble getting it up and running on linux. You can benchmark it by running
script/bench.sh. It works the same way that the CLJS benchmark suite does
I got the lastest SpiderMonkey today (using the instructions from the CLJS wiki)
@spinningtopsofdoom: did you get the minimal case reporting to work w/ my fork?
@spinningtopsofdoom: oh and the changes to test.chuck have been merged so pulling that branch isn’t necessary anymore
@martinklepsch: Yep it looks like it needed to be wrapped in a
deftest to work correctly AFAICT
@spinningtopsofdoom: ok. If wrapping in
deftest is required that’s most likely a more general issue...
@martinklepsch: You can play around with it
lein with-profile test doo node node-test I may be way off base as far as the reporting goes.
ok I gave it shot the results across all the JS engines on my machine are inconclusive
I agree for the graph part, the text benchmarks were good enough to show me if I was way off base. Thanks for confirming the benchmarks I was seeing
@spinningtopsofdoom: have you tried using the Chrome profiler on the
:simple optimized benchmark?
@dnolen yep I've only done high level perf overviews with the profiler. I haven't seen any obvious issues when using
Not right now, tomorrow I have 20% time I can get that too you. You can try
script/profile to build out the profile js I'm using