Chrome app profiling

Question

We are creating a Chrome app that we hope will be released in the coming weeks. We have already sent out a bunch of alpha testers, and despite the fact that the feedback is generally good, we had complaints from users that our extensions are expensive in terms of RAM . We also had reports of processor consumption too high .

Now we have improved what seemed obvious, but we are almost "blind" in terms of execution.

What would be a good strategy for profiling both memory and JS calls for our Chrome app?

Please note that this application is a complete native application, so maybe we can apply some general javascript profiling tips?

Answer 1

As already mentioned, you can use the Chrome developer tools to use memory in memory.

For CPU and RAM, this is not particularly scientific, but you can get a wide checkmark without opening applications, except for Chrome, which has an empty open one and activity monitor for your OS or task manager.

Look at the CPU and RAM readings for Chrome for about: blank, which is about as simple as it is, and compare that with the readings when the application is running.

Disable all extensions to deduce them from the equation.

Hope this helps.