Is it possible to change the 'ClockPrecision' setting of MATLAB's Profiler?
显示 更早的评论
The default ClockPrecision value is apparently 0.001 seconds. If a function or line takes less time than that, it registers as 0. I'm trying to assess the efficiency of a few different algorithms to compare them, but none of them take long enough to round up to 1 millisecond. I could not find any way to change this, since it isn't one of the options like 'timer' and 'history' according to the documentation page:
However, I did find this page:
which does not describe how to change the setting, but shows a different value (100 nanoseconds) than what I have (1 millisecond). I'm hoping that means it can be changed, but I can't figure out how.
Thanks in advance for any help.
采纳的回答
John D'Errico
2015-6-25
编辑：John D'Errico
2015-6-25
1 个投票
Use timeit instead to test and compare specific code blocks. It does various things to make that test far more accurate than the profiler. Steve Eddins had at written at posted it on the file exchange, but it is now part of MATLAB, so no download is needed at all.
While the profiler is very nice and very useful to identify problems in your code, you need a tool like timeit to truly optimize performance once you know where the problem lies.
5 个评论
Nathan
2015-6-25
Walter Roberson
2015-6-25
tic and toc record how long one particular execution took. timeit runs the code many times to reduce the uncertainty of measurement and effects such as the time it can take to parse code the first time it is encountered.
John D'Errico
2015-6-25
IMHO, do NOT use tic and toc for any kind of accurate assessment.
The problem is that there are many reasons why a time assessor may mis-estimate the time taken.
1. On modern CPUs, there are many things happening at once. Stuff happens in the background, often at random. Be careful not to use your web browser or check your mail in the middle of a long time test. You need to make multiple calls to the code to try to average the noise out. Timeit is intelligent, running code that is fast MANY times inside a loop to get the most benefit from variance reduction in a large sample.
2. The first call to a function will always be slower than successive calls, because MATLAB must parse the code and put it into cache. In fact the second call is often a bit slower too. So I often tend to do several time tests to make sure I am seeing a stable prediction. I recall that timeit actually runs your code several times up front (tossing out the time for those initial calls) just for this reason.
3. A code block timed directly at the command line may be different in terms of the time required for code inside a function. This is because the parser may be able to optimize code when it does the parsing, whereas code typed in on the command line see no such benefit. Since code passed into timeit is run as a function inside the function, I believe it will yield a better estimate of how you will be using it because it takes full advantage of any acceleration that will happen.
So given that timeit is available, I would always use it preferentially. I do use tic and toc occasionally, but only for places where I just want to report a rough estimate of the time taken.
Nathan
2015-6-26
Walter Roberson
2015-6-26
Later versions of MATLAB can do a fair bit more optimization of expressions at the command line, apparently. For many years, commands at the command line and code in scripts were unoptimized.
更多回答（1 个）
Philip Borghesani
2015-6-26
The ClockPrecision is based on the timer used, change the profile timer source for a different precision. If you have access to R2015b the processor timer gives the highest precision.
profile -Timer real %
类别
在 帮助中心 和 File Exchange 中查找有关 Performance and Memory 的更多信息
产品
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!
Translated by 
