This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-06-10
Channels
- # admin-announcements (2)
- # arachne (2)
- # beginners (53)
- # boot (52)
- # cider (7)
- # cljs-dev (61)
- # cljsrn (12)
- # clojure (61)
- # clojure-greece (22)
- # clojure-nl (16)
- # clojure-russia (103)
- # clojure-spec (84)
- # clojure-uk (15)
- # clojurescript (137)
- # community-development (14)
- # cursive (4)
- # datomic (14)
- # devcards (6)
- # euroclojure (3)
- # funcool (26)
- # hoplon (27)
- # jobs (4)
- # lambdaisland (1)
- # leiningen (1)
- # om (75)
- # onyx (77)
- # planck (15)
- # proton (2)
- # re-frame (23)
- # ring-swagger (9)
- # schema (1)
- # specter (95)
- # untangled (124)
- # yada (27)
@danielcompton: thank you! i’ve decided for the time being to copy over all the benchmarks from cljs repo and later focussing on the quality of the results themselves.
Generated code size that is
Not really sure, but it's good to keep an eye on it. There have been regressions in the past
@danielcompton: oh cool. i think it should be possible to add that.
@danielcompton: no, tickets should only report how to reproduce with ClojureScript only
I’ve just updated my benchmarks to include all the benchmarks from cljs repo. I had to run the benchmarks through simple benchmarking code to achieve it though. https://ducky427.github.io/clojurescript-benchmarks
just include the minimal source to repro and describe the problem - don’t link to anything
@jr the protocol should not be a var - you should create an example that always shows it to be the case
@rohit that looks really cool! If possible, perhaps a different color choice for JSC and SM. Nearly impossible to see the differences. (Red/green color blind.)
@rohit: I think there are online tools you can use to simulate the various forms of color blindness and see if the choices look differentiable.
btw, the entire dataset is here: https://github.com/ducky427/clojurescript-benchmarks/blob/gh-pages/data.csv
(Sorry for the superficial feedback, but that’s the first thing I noticed. Will dig deeper into the actual content.)
@mfikes: next week i may run these benchmarks through benchmark.js. those take a really long time to run. ~10sec per benchmark and I have about 150 benchmarks in there. so about 30min per suite. I am benchmarking against 14 versions.
@bhauman: looks like I got confused by http://dev.clojure.org/jira/browse/CLJS-1648
@rohit Perhaps if there is an actual server to run the benchmarks, they can take a long time to run without any real consequence.
wow a lot of graphs great!
@bhauman: just bumping about that patch if you want it in a release - cutting one today
@jr if you want a fix for your Var issue in the release going to need more feedback as requested above
my suspicion is that Schema adds some :protocol
meta, if this is not a symbol we now throw it away
dnolen: unfortunately that still errors with the same exception. I’m still trying to put together reproducible repo, but have been told not to utilize my work time on it 😞
I’m running into an error with :simple
compilation that doesn’t occur with any other type of optimizations
has anything like this ever been reported?
the error is $s$$.substring is not a function
and seems related to cljs.pprint
@anmonteiro: maybe there’s been something like that in the past yes
from what I can gather from the stacktrace
if you’re shipping cljs.pprint than you’re treading into waters where very little time has been spent
weird thing is it works in :advanced
, so it’s good to go!
It’s devcards that uses pprint
I’m trying to compile some cards with optimizations, and ran into this thing
I’ll use :advanced
anyways