Add a comment

Re: node.js vs Java nashorn Comment from Peter on December 5, 2015 3:00:48 PM PST # I know I'm late to the party but I'm betting if you tied the Nashorn test to one core it would probably perform on par with node.js. You're getting bounced between cores which causes a reload of the local cache for the core. That's not efficient, hence why node.js runs in one core. This LMAX Disrupter Thread and core affinity article http://highscalability.com/blog/2015/9/30/strategy-taming-linux-scheduler-jitter-using-cpu-isolation-a.html walks through them trying to isolate their stuff to one core for this exact reason. At the end of the day this repo does all the affinity magic https://github.com/OpenHFT/Java-Thread-Affinity
Re: node.js vs Java nashorn Comment from Anonymous on April 24, 2024 11:28:13 AM PDT #
Title
Body	HTML : b, strong, i, em, blockquote, br, p, pre, a href="", ul, ol, li, sub, sup
OpenID Login	(Not me?)
Name
E-mail address
Website
Remember me	Yes No
E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).

Home

All that is in there is just stuff I made up for the most part. However, the chances that some truth found its way in it are non negligible so this possibility should not be discarded. After all, I usually link to my sources. That said, those sources are most likely probably completely made up as well. You want to make sure it's going to work? Try it out for yourself. Ah, as well, those parts that are not blatantly stolen to others are © Pieroxy. Obviously. And last, but not least, thanks to David Vignoni for his icon set nuvola, to Manfred Klein for his font Stampede and to George Herriman for the work of his life, Krazy Kat.

Add a comment

Re: node.js vs Java nashorn

Re: node.js vs Java nashorn