News for hackers. Stuff that matters.

A comment on Speeding up the JavaScript ecosystem – one library at a time. Parent comment

Re:Speeding up the JavaScript ecosystem – one library at a time by AtlasBarfed on Tuesday November 29, 2022 @07:43PM (#33795417)
"really, really fast"

Compared to what? Polar bears?

Here: is it faster than warm JVM?

[ Parent | on HN ]
Re:Speeding up the JavaScript ecosystem – one library at a time by winrid on Tuesday November 29, 2022 @08:01PM (#33795554)
V8 is almost never faster than a warm JVM, especially once you get to heap sizes bigger than a couple GB.

You can't even store more than 14m or so keys in a map in Node w/o reaching for an off heap solution due to hard limits in the runtime...

[ Parent | on HN ]
Re:Speeding up the JavaScript ecosystem – one library at a time by fabiospampinato on Tuesday November 29, 2022 @11:44PM (#33797102)
If needed you can make your own map that doesn't let you down: https://www.npmjs.com/package/infinity-map
[ Parent | on HN ]
Re:Speeding up the JavaScript ecosystem – one library at a time by winrid on Wednesday November 30, 2022 @01:11AM (#33797548)
I've used megahash with great success:

https://github.com/jhuckaby/megahash

[ Parent | on HN ]
Re:Speeding up the JavaScript ecosystem – one library at a time by ptrwis on Tuesday November 29, 2022 @08:27PM (#33795757)
I would freeze before the JVM would warm up.
[ Parent | on HN ]
Re:Speeding up the JavaScript ecosystem – one library at a time by winrid on Wednesday November 30, 2022 @01:12AM (#33797555)
Jokes aside, then maybe your code cache size is too small ;p
[ Parent | on HN ]