This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-11-30
Channels
- # beginners (126)
- # boot (2)
- # cider (6)
- # cljs-dev (46)
- # cljsjs (8)
- # clojure (122)
- # clojure-greece (57)
- # clojure-italy (6)
- # clojure-poland (3)
- # clojure-russia (2)
- # clojure-serbia (5)
- # clojure-spec (26)
- # clojure-uk (99)
- # clojurescript (39)
- # cursive (15)
- # datascript (7)
- # datomic (21)
- # dirac (7)
- # duct (1)
- # emacs (19)
- # fulcro (58)
- # garden (4)
- # graphql (15)
- # hoplon (2)
- # immutant (1)
- # instaparse (3)
- # jobs (5)
- # juxt (15)
- # klipse (4)
- # leiningen (2)
- # lumo (52)
- # off-topic (8)
- # om (27)
- # onyx (22)
- # other-languages (3)
- # portkey (2)
- # protorepl (2)
- # re-frame (7)
- # reagent (7)
- # ring (11)
- # rum (7)
- # shadow-cljs (114)
- # spacemacs (20)
- # specter (16)
- # test-check (5)
- # timbre (1)
- # unrepl (43)
- # yada (17)
I have a very big map to transmit to the browser. Is there a way to make use of multiple cores when formatting the data? As it is I have 1 CPU going to 100% for a few seconds...
Tho I guess transit is possible
Does it mean it would start sending before it completed the formatting?
I think yada/json is actually wrong here, I remember seeing something and going "wtf? why would it do that!"
Hmm... not multi threaded, but that might be even better.
I mean : I don't know if it's single thread yet, but it would be better than simply doing everything in multiple threads and THEN sending it.
I'd benchmark, as it might be the GC killing you or something related to the formatting itself.
for sure
@frozenlock how big are you talking about? 1MB, 10MB, 100MB?
@danielcompton 10-100MB