Ladies and Gentlemen.
Thank you.
We're getting even better numbers on other devices:
Android phone, ~5M ops/sec . Macbook Air, Chrome, ~30M ops/sec . Macbook Pro, Chrome Canary, ~80M ops/sec . How did we accomplish 100,000 ops/sec in IE6?This test ran on the cheapest windows laptop I could find on the market. A $150 2GB Atom CPU which I loaded up with IETester to do some performance benchmarking. Getting these numbers has been hard work. For those who want the real answer, check out our Read the Source podcast:
For those who want the short summary:
Use PTSD (Performance Testing Speed Development) to micro-optimize your code without getting lost in micro-optimizations. More on PTSD to come in the future. Reduce function calls and prioritize hot code paths as the first if statements. Do work only once, then use centralized caching and cache updating to skip ever doing work again.Resulting caveats:
These tests are running on the bleeding edge 0.5 branch, only 15% of the API tests are currently passing. These performance benchmarks rarely have cache misses, but many other database benchmarks do the same. Measuring disk I/O isn't very interesting. Take all performance testing benchmarks with a huge grain of salt. That is why we're working onpanic, a distributed testing runner.Hop on the gitter to learn more and chat with us!