Inaccurate measurements of time (under some/all conditions?)

[ceefour]

From Ephraim Rubenstein [email protected] :

I downloaded 3 Cachegrind viewers today.

1. WebCacheGrind 1.1.0.16
2. WebGrind and
3. QCacheGring

WebCacheGrind is showing measurements approx 1/10 of the other 2

WebCacheGrind Zend\MVC\Application->init 49ms WebGrind 492ms and QCacheGrind 492 253 (microsecs)

This does not make sense .

Can you advise?

TIA

Efffy

[bbak]

Same here. Version 1.0.0.14 (last one on Sourceforge) reports 9731 ms and current 1.1 973ms on the same .out file. A xdebug Profile is also ~ 9 Sec.

[augmenter]

I can confirm, 1.10.16 shows 14ms, while 1.0.0.14 shows 142ms.

1.0.0.14 above image, 1.10.16 below

[FractalizeR]

Same here

[ceefour]

I don't know when or if there'll be a fix. Feel free to use an older version at https://github.com/ceefour/wincachegrind/releases

[FuryBart]

I can confirm the problem with the latest version. All times are 1/10 of the times in the cachegrind files. You can easily test it with just sleep(1) in a php file. Funny enough, the problem is well kown since at least 8 years. See the issues at Sourceforge: https://sourceforge.net/p/wincachegrind/bugs/2/ Merijn Bosma said there, that he has fixed the issue in release 10.0.0.14. So someone has "fixed" it back. It's even possible to work with that issue, but how hard could it be to add a multiplier of 10 to the times? Just an idea.