This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-06-01
Channels
- # announcements (7)
- # babashka (72)
- # beginners (62)
- # biff (1)
- # calva (9)
- # cider (8)
- # clj-kondo (35)
- # clj-otel (8)
- # cljsrn (11)
- # clojure (98)
- # clojure-europe (25)
- # clojure-germany (1)
- # clojure-norway (9)
- # clojure-uk (2)
- # clojured (3)
- # clojurescript (12)
- # conjure (3)
- # core-logic (4)
- # cursive (18)
- # datalevin (9)
- # datomic (5)
- # defnpodcast (2)
- # exercism (1)
- # graalvm (5)
- # gratitude (6)
- # hyperfiddle (3)
- # interop (12)
- # jobs (1)
- # joyride (34)
- # lsp (22)
- # meander (14)
- # missionary (16)
- # nbb (88)
- # off-topic (4)
- # pathom (20)
- # podcasts-discuss (1)
- # polylith (13)
- # portal (10)
- # re-frame (6)
- # releases (2)
- # remote-jobs (2)
- # rewrite-clj (3)
- # shadow-cljs (3)
- # spacemacs (6)
- # vim (24)
Hi, when we use an event handler to actually perform a heavy task (serializing a whole 3d scene + uploading it to a server), there is a risk of cpu hog and the interface might be unresponsive for some time. But I noticed that in some browsers (Metamask for instance) the interface might get unresponsive forever. Is it an expected behavior? Is there a pattern to perform this kind of task (setTimeout or something different) ? Another solution would be to actually split the file to upload in several chunks and send each one separately to have a better interaction with reframe pipeline.
It's not expected - my knee-jerk reaction would be to blame the browser (I've had enough instance where it was the case). For all expected CPU hogs, there are some solutions here: https://day8.github.io/re-frame/Solve-the-CPU-hog-problem/
Another potential solution is to use a web worker. But it doesn't work in all cases, so you gotta reason about it and maybe try and measure.
I blamed the browser too (especially because it only happens with this one (Metamask)). Ok, I'm going to think about a way to circumvent the issue. Thank you!
In some cases of CPU-hungry code, it may be worth considering web workers e.g. https://github.com/jtkDvlp/re-frame-worker-fx I havn't used that fx myself but the impl looks reasonable. There are some obvious caveats, such as you need to serialize the input to the web worker to be able to send it to the web worker - so for an issue like serializing a large 3d scene it may not help you at all since you'll need to serialize it to pass it to the web worker. But it is worth keeping in mind as an escape hatch from the main single UI thread in some circumstances.