This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-10-24
Channels
- # aws (7)
- # aws-lambda (3)
- # beginners (65)
- # boot (43)
- # cider (7)
- # cljs-dev (12)
- # cljsrn (15)
- # clojure (284)
- # clojure-austin (32)
- # clojure-brasil (4)
- # clojure-dusseldorf (4)
- # clojure-germany (1)
- # clojure-italy (40)
- # clojure-spec (21)
- # clojure-uk (69)
- # clojurescript (97)
- # core-async (11)
- # cursive (19)
- # data-science (1)
- # datascript (6)
- # datomic (30)
- # dirac (2)
- # emacs (4)
- # events (2)
- # fulcro (76)
- # graphql (38)
- # juxt (1)
- # lein-figwheel (1)
- # leiningen (6)
- # luminus (4)
- # lumo (13)
- # mount (4)
- # off-topic (24)
- # om (28)
- # onyx (32)
- # other-languages (1)
- # parinfer (40)
- # pedestal (1)
- # portkey (47)
- # re-frame (21)
- # reagent (4)
- # ring (4)
- # ring-swagger (3)
- # rum (1)
- # shadow-cljs (115)
- # spacemacs (5)
- # sql (14)
- # unrepl (1)
- # yada (3)
@mfikes I'm curious: Do you have some kind of benchmarking setup to test all the engines together? Do you have that in a repository?
script/benchmark runs them, and there’s a corresponding cljs file containing the actual benchmarks
Right @rauh, and I simply have the engines set up as per https://clojurescript.org/community/running-tests
Tip: I usually temporarily delete all of the other benchmarks outside of the ones I'm interested in to eliminate extra cruft to look at
@mfikes I see, I haven't run it in a while. I didn't realize it'd run all engines and format the output.
Btw, I agree with your select-keys
benchmarks. I tried a few other things, but nothing stood out
Yep, it's about the only way I get a sense of trust that perf gains actually work. (As we all know, you can try so many approaches that actually don't really pan out.)
In https://dev.clojure.org/jira/browse/CLJS-2383, I really expected that the stuff from CLJ-1789 might be better, but the perf tests don't lie, and evidently a simple change to use keyword-identical?
is sufficient to get the perf gain.
Yeah I expected lookup-sentinel
to also be faster. I got better numbers at first, but once the JIT of the JS engines kicks in it's just a toss up. Also, I sometimes got better performance with reduce, but then slower perf on other browsers... Tough call.
can :global-exports
be called as functions?
(require '[cljsjs.codemirror :as codemirror])
(codemirror ...) ;; <-- use of undeclared var codemirror
should
it was a build tool problem, works as expected now, thanks