This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-03-29
Channels
- # announcements (9)
- # aws (1)
- # beginners (133)
- # boot (2)
- # calva (94)
- # cider (48)
- # cljdoc (7)
- # cljsrn (22)
- # clojure (128)
- # clojure-europe (22)
- # clojure-finland (7)
- # clojure-greece (6)
- # clojure-losangeles (3)
- # clojure-nl (81)
- # clojure-spec (30)
- # clojure-uk (60)
- # clojure-ukraine (1)
- # clojurescript (45)
- # core-async (26)
- # cursive (18)
- # datomic (12)
- # defnpodcast (1)
- # duct (4)
- # editors (4)
- # emacs (6)
- # fulcro (37)
- # graphql (4)
- # jobs (2)
- # jobs-rus (1)
- # juxt (7)
- # kaocha (2)
- # leiningen (1)
- # nrepl (22)
- # off-topic (2)
- # re-frame (16)
- # reagent (8)
- # reitit (22)
- # ring-swagger (5)
- # shadow-cljs (81)
- # tools-deps (4)
@borkdude no, there is not. What kind of tests you would like to see? Maybe all of encoding, decoding & encoding+decoding on the JVM? Current perf tests are here: https://github.com/metosin/jsonista/blob/master/test/jsonista/json_perf_test.clj
btw, now looking at the perf numbers, I think the spec+jsonista combo would enable some good optimizations on perf on decode. As we would know the form of the maps, we could precreate the (Immutable) maps before decode. Setting a value for a known key in pers.array-map is Much faster than adding a key.
My quess is that it would be 2x faster (based on similar optimizations in reitit wildcard param handling)
I've recently evaluated different ways of writing/readinig clojure data and (unless I benchmarked something incorrectly) Jsonista turned out to be the fastest so I went with it.