Profiler issue

Hi,

I’m currently working on performance optimizations using the profilers, but I'm seeing some very inconsistent results. In several cases, extremely simple functions appear to take disproportionately long to execute according to the profiler.

One example that strongly suggests a potential issue with the profiler is the following:

Both of these functions are nearly identical:

public function getLabelColor() as ColorType? { return _labelColor; }
public function getValueColor() as ColorType? { return _valueColor; }

Despite this, the reported execution times differ significantly.

Has anyone encountered similar behavior or have an explanation for these numbers - aside from a profiler bug?

the-ninth 15 days ago

Another issue I’ve encountered is that the profiler data appears to be incomplete.

For example, I use several Array functions in my code. While Array.add() and Array.addAll() show up in the profiler, calls to Array.size() and Array.remove() do not appear at all.

This might be related to an issue I reported earlier, where profiler entries are mislabeled:
https://forums.garmin.com/developer/connect-iq/i/bug-reports/incorrect-background-registerforsleepevent-entries-in-profiler

andyj713 14 days ago in reply to the-ninth

I dealt with this a few years ago https://forums.garmin.com/developer/connect-iq/f/discussion/2479/optimization-guidelines/1657741#1657741. Sorry, but the profiler is a tale of woe.