Thanks for leading this reveman@!
Is there a performance dashboard that will show us how we improve over time and where we should prioritize?
I did not see anything about it in go/chrome-os-ui-performance

We're still trying to determine what is the best way to measure improvements and prevent regressions. We're leaning towards adding ash/mash_perftests that contain the specific cases we care about and collect numbers such as "overdraw" and "raster". These test results can then be hooked up to a performance dashboard so it's easy to follow progress and track regressions.

Triage nag: This Chrome OS bug has an owner but no component. Please add a component so that this can be tracked by the relevant team.