One some machines (e.g. Gerrit's), there is pretty high CPU/GPU usage in Tidepool Web, even when there's no data in the account. The Chrome Task Manager shows the "GPU Process" running at around 80% and the Tidepool Tab process running at around 40%. When switching to another tab, both processes drop to <5%.
Create account on dev (fix applied)
Visit the basics, daily, bgLog, trends, and settings views and record CPU Usage
Visit the basics, daily, bgLog, trends, and settings views with a `?animateStats=false` query param set and record CPU usage
Ensure that the idle CPU usage drops down to nearly zero, and for the most part stays there after a short wait while the loading activity wraps up.
Test Verification Doc:
Unable to upload devices to the new dev environment for testing. Currently working it out with Derrick. Will resume testing after solving.
waiting on changes for web-36
QA ✔ Pass
The ?animateStats=false query parameter to halt the stat animations results in CPU usage dropping to zero after the page has loaded. This infers that the loading dot animations that were constantly running in the background (hidden by CSS) causing high CPU usage are no longer consuming background CPU cycles due to this fix.
Deployed to `int` and `prd`