This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-06-16
Channels
- # arachne (1)
- # beginners (27)
- # boot (17)
- # cider (10)
- # cljs-dev (5)
- # cljsrn (76)
- # clojure (59)
- # clojure-austin (2)
- # clojure-brasil (1)
- # clojure-greece (76)
- # clojure-mexico (1)
- # clojure-quebec (63)
- # clojure-russia (16)
- # clojure-spec (127)
- # clojure-uk (12)
- # clojurescript (72)
- # community-development (7)
- # core-async (3)
- # core-matrix (2)
- # cursive (13)
- # datomic (8)
- # emacs (4)
- # funcool (4)
- # hoplon (148)
- # immutant (5)
- # keechma (2)
- # lambdaisland (5)
- # lein-figwheel (15)
- # leiningen (20)
- # off-topic (23)
- # om (13)
- # om-next (19)
- # onyx (11)
- # planck (11)
- # re-frame (59)
- # reagent (14)
- # rum (34)
- # specter (30)
- # spirituality-ethics (16)
- # uncomplicate (5)
- # untangled (387)
- # yada (2)
If anyone is interested, I’ve re-run micro benchmarks for 14 versions of ClojureScript using Benchmark.js and the results are here: https://ducky427.github.io/clojurescript-benchmarks
These were run on a linux box on JSC/SpiderMonkey/v8 engines and they took 8hrs in total. All documentation for running them on your machine are here: https://github.com/ducky427/clojurescript-benchmarks/blob/master/README.md
There is ability in the project to run quick benchmarks as well which take significantly less time (~ 2-3 minutes per cljs version)
@kamn: thanks! I need to so spend some time studying the results. there are some funky results. For example, the results for symbol
benchmark http://blog.ducky.io/clojurescript-benchmarks/full/20160614.html#bench-2 . The strangeness disappears when I only run that benchmark. So ¯\(ツ)/¯