Agreed that the optimizations are kinda wonky with crankshaft / hydrogen etc. I wonder if more insight could be shown, or if there was a way to test it without the crankshaft / hydrogen anymore. JSC though is just as competitive more most tasks, in some better, in some the same, in some not. However, the 99% of people are probably not going to peg CPU, but this does make me think again about worker pools (god bless .fork and sending handles).
On Friday, May 25, 2012 2:50:37 PM UTC-5, Jorge wrote: > > On May 25, 2012, at 8:02 PM, Bradley Meck wrote: > > > It may not be the speed champion, but its the API champion. For example > Chakra in IE is stupid good at GC and Code-Gen speed (time to generate > rather than run speed). > > Yes, the API is great. And it's easy(er) to build and embed than say, JSC > or spidermonkey, and comes with (some) documentation, and it's what node > uses (and we love node). > > But it's taking over 3 seconds to run a loop, and that's not right. > Clearly. > -- > Jorge. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
