Merge \"docs: remove out-of-date performance info\" into nyc-dev

need to solve. Make sure you can accurately measure your existing performance,

or you won't be able to measure the benefit of the alternatives you try.</p>

<p>Every claim made in this document is backed up by a benchmark. The source

to these benchmarks can be found in the <a

href="http://code.google.com/p/dalvik/source/browse/#svn/trunk/benchmarks">code.google.com

"dalvik" project</a>.</p>

<p>The benchmarks are built with the

<a href="http://code.google.com/p/caliper/">Caliper</a> microbenchmarking

framework for Java. Microbenchmarks are hard to get right, so Caliper goes out

of its way to do the hard work for you, and even detect some cases where you're

not measuring what you think you're measuring (because, say, the VM has

managed to optimize all your code away). We highly recommend you use Caliper

to run your own microbenchmarks.</p>

<p>You may also find

<a href="{@docRoot}tools/debugging/debugging-tracing.html">Traceview</a> useful

for profiling, but it's important to realize that it currently disables the JIT,