I kind of figured it had to be jsperf. I was stumped as to how a test case that was doing less was performing worse. Lesson learned, don't trust jsperf.
On Tuesday, April 30, 2013 12:56:39 PM UTC-7, Eldar wrote: > > Huh, and don't use setTimeout() yourself :) > > Basically, you should just make all your benchmarks sync. e.g. > > var d = new Promise > d.then(noop) > d.resolve() > > That will give you right numbers. > > On Tuesday, April 30, 2013 8:51:23 PM UTC+4, mgutz wrote: >> >> Does anybody see anything wrong with the logic in these tests? >> >> http://jsperf.com/promise-comparisons/13 >> >> I expected callbacks to be faster than promises. >> > -- -- 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 --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
