This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-12-10
Channels
- # admin-announcements (32)
- # announcements (4)
- # aws (25)
- # beginners (296)
- # boot (1)
- # cider (87)
- # clara (16)
- # cljs-dev (7)
- # cljsrn (41)
- # clojure (121)
- # clojure-art (26)
- # clojure-japan (4)
- # clojure-miami (190)
- # clojure-russia (168)
- # clojure-sg (3)
- # clojure-sweden (13)
- # clojurescript (138)
- # clojurex (7)
- # cursive (98)
- # data-science (2)
- # datomic (129)
- # devcards (10)
- # editors (5)
- # funcool (1)
- # hoplon (31)
- # jobs (1)
- # ldnclj (4)
- # lein-figwheel (3)
- # off-topic (2)
- # om (213)
- # onyx (33)
- # parinfer (7)
- # portland-or (1)
- # re-frame (19)
- # reagent (2)
- # ring-swagger (27)
- # slack-help (3)
@dnolen & @alexmiller I've improved the Lean HAMT perf for seqs to ~30%- 40% of the current HAMT implementation for all the JS engines (except FF). For small maps (<= 100) the perf differs narrows. It seems the perf improvements for the paper are born out in practice. I'll be working on improving hash
and =
next
@spinningtopsofdoom: very cool! what changes did you have to make for the perf bumps?
Changing the iterating over the sub nodes from inc to the number of sub nodes to dec to 0. That allowed me to have a a custom array copy function of an array of size 7. Those were the main perf bumps
@spinningtopsofdoom: do you have a repo with those impls?
The stack iteration that was used by the paper was designed for mutable oop so there was some allocation overhead that needed to be trimed for a seq based immutable version
@bronsa: Here's the repo https://github.com/bendyworks/lean-map