Sunday, January 6, 2013

Optimizing the speedometer for speed responsiveness and CPU consumption

As it goes, adding new features over time tends to lead to some performance issues. I'm used to run the full profiling round from time to time, and time for the next one came just this evening :).

So here is the graph before the today's optimizations:

And after:

So, except for the initial app start, that still has almost the same CPU/time requirements, for the app running and showing the samples of speed the CPU and time to process is cut down to 1/3 of what it used to be.

Those optimizations will be available in January release that I'm preparing just right now. In the subsequent posts, I'll describe what all new features are going to be added.