blocks|key|1126003|text|您可以使用Traceview。它远非理想，但却是可行的。This+article介绍了如何使用它。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1126004|entityMap|0|LINK|mutability|MUTABLE|url|http://developer.android.com/tools/debugging/debugging-tracing.html^0|S|C|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

You can use Traceview. It is far from ideal, but works. 
<a href="http://developer.android.com/tools/debugging/debugging-tracing.html" rel="noreferrer">This article</a> describes how to use it.

blocks|key|1126082|text|这取决于你要测试什么。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1126083|如果你为Android开发应用程序，你应该尝试一下TimingLogger类。看一下描述TimingLogger帮助器类用法的this+article。|offset|length|1126084|一个非常好的工具是JMeter，还有一个plugin+for+Android。|1126085|如果您不想使用外部工具，而是一种非常标准的方法来测量运行时间，则必须使用System.nanoTime()。你不应该使用currentTimeMillis，因为它测量的是挂钟时间，因为没有一台计算机的时钟是完美的(它们偶尔都需要修正)，有一个进程在运行，并不断地对系统时钟进行微小的修正。更不用说闰秒修正了。|1126086|尽管经常使用currentTimeMillis，但测量已用时间和时间仍然是不正确的。无论如何，由于调用需要一些时间，所以您不应该期望对非常非常小的时间间隔进行正确的计时。但对于Android来说，这应该不是问题。|1126087|我将向您展示一个示例：|1126088|long+startTime+=+System.nanoTime();

//+run/call+the+method

long+endTime+=+System.nanoTime();
long+diff+=+endTime+-+startTime+;
System.out.println("Elapsed+milliseconds:+"+%2B+diff+/1000000);|code-block|syntax|javascript|1126089|你也可以看看这个免费的库：http://jetm.void.fm/。|1126090|你也可以找到JMeter的教程。|1126091|entityMap|0|LINK|mutability|MUTABLE|url|http://hoccer.com/2010/09/measuring-performance-with-android/|1|https://jmeter.apache.org/|2|http://jmeter-plugins.org/wiki/AndroidDriverConfig/|3|http://jetm.void.fm/|4|http://www.tutorialspoint.com/jmeter/^0|0|1R|C|0|0|9|6|1|K|I|2|0|0|0|0|0|D|K|3|0|6|6|4|0^^$0|@$1|2|3|4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1D|8|@]|9|@$D|1E|E|1F|1|1G]]|A|$]]|$1|F|3|G|5|6|7|1H|8|@]|9|@$D|1I|E|1J|1|1K]|$D|1L|E|1M|1|1N]]|A|$]]|$1|H|3|I|5|6|7|1O|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1P|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|N|3|O|5|P|7|1R|8|@]|9|@]|A|$Q|R]]|$1|S|3|T|5|6|7|1S|8|@]|9|@$D|1T|E|1U|1|1V]]|A|$]]|$1|U|3|V|5|6|7|1W|8|@]|9|@$D|1X|E|1Y|1|1Z]]|A|$]]|$1|W|3|-4|5|6|7|20|8|@]|9|@]|A|$]]]|X|$Y|$5|Z|10|11|A|$12|13]]|14|$5|Z|10|11|A|$12|15]]|16|$5|Z|10|11|A|$12|17]]|18|$5|Z|10|11|A|$12|19]]|1A|$5|Z|10|11|A|$12|1B]]]]

It depends what're you going to test.

In case you develop applications for Android you should try out the TimingLogger class. Take a look at <a href="http://hoccer.com/2010/09/measuring-performance-with-android/" rel="noreferrer">this article</a> describing the usage of the TimingLogger helper class.

A very good tool is <a href="https://jmeter.apache.org/" rel="noreferrer">JMeter</a> and there is a <a href="http://jmeter-plugins.org/wiki/AndroidDriverConfig/" rel="noreferrer">plugin for Android</a> as well.

if you don't want to use external tools, but a very standard way, to measure elapsed time, you must use System.nanoTime(). You shouldn't use currentTimeMillis, because it measures wall-clock time ans, as no computer's clock is perfect (them all occasionally needs to be corrected) there's a process that runs and continually issues small corrections to the system clock. Not to mention the leap second correction.

Although currentTimeMillis is often used, it's still incorrect to measure elapsed time and timing. Anyhow, as the invocation takes some time, you should not expect to correctly time very very small intervals. But that shouldn't be an issue working with Android.

I'll show you an example:

<pre><code>long startTime = System.nanoTime();

// run/call the method

long endTime = System.nanoTime();
long diff = endTime - startTime ;
System.out.println("Elapsed milliseconds: " + diff /1000000);
</code></pre>

You could have a look at this free library as well: <a href="http://jetm.void.fm/" rel="noreferrer">http://jetm.void.fm/</a> .

You can also find tutorial for <a href="http://www.tutorialspoint.com/jmeter/" rel="noreferrer">JMeter</a> as well.

blocks|key|911072|text|在http://developer.android.com/training/articles/perf-tips.html中推荐的另一个工具是Caliper：https://code.google.com/p/caliper/。(我没有用过它，所以我对它了解不多。)|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|911073|entityMap|0|LINK|mutability|MUTABLE|url|http://developer.android.com/training/articles/perf-tips.html|1|https://code.google.com/p/caliper/^0|1|1P|0|28|Y|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

Another tool recommended in <a href="http://developer.android.com/training/articles/perf-tips.html" rel="nofollow">http://developer.android.com/training/articles/perf-tips.html</a> is Caliper: <a href="https://code.google.com/p/caliper/" rel="nofollow">https://code.google.com/p/caliper/</a>. (I haven't used it, so I don't know much about it.)

I need to find where the bottlenecks are in my Android app.

What profiling tools or techniques can I use?

How can I profile my Android app?

Android

我需要找出我的Android应用程序中的瓶颈所在。我可以使用哪些分析工具或技术？

问如何分析我的Android应用程序？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何分析我的Android应用程序？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何分析我的Android应用程序？
EN