Re:Node.js memory benchmark confirms V8's GC may not be read...
by robin_reala on Wednesday September 29, 2010 @11:10AM
(#1739667)
Has anyone done any experiements with node.js and Jägermonkey? They’re getting pretty close to V8 in speed ( http://arewefastyet.com/ ) and might prove better for server use (utter conjecture on my part).
[ Parent
| on HN ]
Re:Node.js memory benchmark confirms V8's GC may not be read...
by midnightmonster on Wednesday September 29, 2010 @11:30AM
(#1739753)
My understanding is that the Xmonkeys are not nearly so amenable to embedding as node. There are some server implementations of older monkeys, though:
* whitebeam http://whitebeam.org/, which to my surprise appears to be not actually dead yet.
* jaxer http://jaxer.org/
* couchdb
But none of these seem to be low level enough to make a reasonable comparison.
Flusspferd http://flusspferd.org/ seems most like node, but using spidermonkey (circa Firefox 3.5, it seems, but actively maintained, so there's hope for future enhancements). Unfortunately, it doesn't yet seem to have all the handy web serving stuff that node has, so probably still not useful for a competitive benchmark.
Re:Node.js memory benchmark confirms V8's GC may not be read...
by sh1mmer on Wednesday September 29, 2010 @11:31AM
(#1739758)
I talked with Brendan Eich in New York after JSConf.eu and he was suggesting they might be looking at porting the V8 API to Jägermonkey after they release it so that it can run Node.