Performance Profiling Weirdness?

What did I do wrong here... simply grabbing the millisecond timer before and after a collection of compute() logic calls. Why would I get random 0 millisecond durations? No way these calls take less than 1ms. I believe the 15-16ms values, I think.

0 jim_m_58 over 4 years ago

The millisecond timer in the sim is not reliable.

In the 4.1.0-beta1 SDK there is an actual profiler. You can use it with any device. I did another post about it earlier today:

https://forums.garmin.com/developer/connect-iq/f/discussion/2479/optimization-guidelines/1389851#1389851

0 Travis.ConnectIQ over 4 years ago

This is the underlying source of the issue you are seeing.

The resolution of the GetTickCount function is limited to the resolution of the system timer, which is typically in the range of 10 milliseconds to 16 milliseconds. (https://docs.microsoft.com/en-us/windows/win32/api/sysinfoapi/nf-sysinfoapi-gettickcount)

We could update our System.getTimer() API to use the high-resolution timer functionality provided by Windows. I'm not sure how it would be prioritized, but this could be considered an enhancement.. if it were in the Bug Reports area.