Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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

Browse Source
This commit is contained in:
Mark Lu
2016-07-11 20:12:32 +00:00
committed by Android (Google) Code Review
parent 0e6f2097d3 ff51bffb34
commit 62f199ed9f
1 changed files with 2 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
docs/html/training/articles/perf-tips.jd
View File

@@ -401,19 +401,6 @@ final fields too.)
need to solve. Make sure you can accurately measure your existing performance, 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> 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 <p>You may also find
<a href="{@docRoot}tools/debugging/debugging-tracing.html">Traceview</a> useful <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, for profiling, but it's important to realize that it currently disables the JIT,