I came across the very handy-looking Undersore.js today, and clicked on the test & benchmark link. I first ran the test in Chrome. The results below show number of operations per second. Looks like each, map, keys, values, and range are pretty inexpensive operations, whereas uniq and intersect should be used sparingly. All makes sense. Then out of curiosity, I ran the same tests in IE and Firefox. The exact numbers are not significant as the results vary by 10-20% between subsequent runs in the same browser, but the range is pretty illustrative. And yes, I know IE9 is harder, better, faster, stronger, so this is not a fair fight. I can’t wait for IE9 to replace every previous IE version… Ops/sec (higher is better) TestChrome 6IE 8Firefox 3.6 _.each() 20213 510 3249 _(list).each() 13570 493 3161 jQuery.each() 3637 209 910 _.map() 18581 303 5488 jQuery.map() 7084 686 8519 _.pluck() 10852 282 4785 _.uniq() 127 1 33 _.uniq() (sorted) 308 210 84 _.sortBy() 1641 45 359 _.isEqual() 4962 869 1826 _.keys() 22675 1142 4295 _.values() 24551 321 5435 _.intersect() 83 1 20 _.range() 33345 1223 5262 Again, why I use Chrome as my default browser.
posted by Oskar Austegard at 8:14 PM on May 24, 2010
"Comparative Performance of Underscore.js in Chrome and IE"
No comments yet. -