Crazy time values in profiler results
object
Posts: 7
I started using ANTS profiles 3.0 and I am getting absurd results. I profiled a few unit tests (using NUnit command line tool), profile showed in a summary page that execution time was about 2 minutes (which is correct), however all method related time values seem to be multiplied by thousands and millions. Individual code lines have times between 1 and 10 millions, and if I check "AllMethod" tab, then for example Dispose method on a database took 32600990000.0000 seconds to execute in total.
I have found an old thread in ANTS profiler 2.0 forum where it was confirmed that there were time computation problems on some machines, and that this was going to be fixed for the next version. Now the next version has come, and I would very much like to see the solution, especially since we just bought the profiler and need to be able to justify our purchase.
Thanks in advance
Vagif Abilov
I have found an old thread in ANTS profiler 2.0 forum where it was confirmed that there were time computation problems on some machines, and that this was going to be fixed for the next version. Now the next version has come, and I would very much like to see the solution, especially since we just bought the profiler and need to be able to justify our purchase.
Thanks in advance
Vagif Abilov
Comments
If you are using an Intel Mobile Pentium processor then you could quite possibly be using SpeedStep which you can normally disable through the bios or through an application in your systray.
Do you get the same results if you try profiling on another PC?
The main advantage of SpeedStep is to improve battery life and I imagine that you will be running ANTS Profiler whilst connected to the mains power. If you disable SpeedStep whilst connected to the mains your battery life won't be affected, you can run ANTS Profiler and your PC would run faster as well (I think!).
I will discuss this with the profiler project manager to see what might be done in the future to improve things and report back to you, but for know the only workaround available is to disable SpeedStep.
It was recommended to go to Power Applet in Control Panel and select the Always On option to disable SpeedStep. It helped although timings still look suspiciously high. For example, Mandelbrot's Form1.Main show now 62 seconds though the execution completed in 5-6. As long as times will increase proportionally and will not reach absurd values, this workaround should be sufficient.
Thank you very much for quick reply. I wonder if other profilers suffer from SpeedStep. If not, then I guess you have a challenge to solve :-)
Best regards!
Vagif
Thank you Vagif for your patience and for your help in diagnosing the problem.