5 ms·
I used it back in the day to provide server side rendering for a Clojure/ClojureScript/Reagent web app. I remember it being a bit of a pig, both in memory cons
by reitzensteinm 6y ago
I used it back in the day to provide server side rendering for a Clojure/ClojureScript/Reagent web app.
I remember it being a bit of a pig, both in memory consumption and CPU use, but I'm sure that was just relative to the black magic behind V8.
- KajMagnus 6y agoI use it for server side rendering, in a Scala web app. It takes a bit to warm up and JIT compile the Typescript code (transpiled to js), but after that, it's okay fast. I did a bit comparison with V8 maybe 5+ years ago and at the time, it was about the same speed as V8, from what I could see in a few quick tests — after warmup a lot.
- reitzensteinm 6y agoThat's very interesting. I am guessing ClojureScript generates a lot more code that runs through interfaces that sophisticated JITs can partially evaluate away. For us, the performance difference was an order of magnitude, to the point that we were too slow in cases for search engines. We were investigating building an external Node proxy instance to prerender pages. I sincerely hope there's no flag or simple tweak we were missing. It's possible the instances were starved for memory, for instance.