Conversation
0fa054a to
48609d8
Compare
|
Without the change in #50842: With it: Numbers from a Pixel 4 so they'll be more exaggerated in the lab. |
|
I wonder why |
|
I split the commits. We don't have to do it in one pr but I added it to make it easier to test changes locally without another device. |
dev/devicelab/manifest.yaml
Outdated
|
|
||
| animated_placeholder_perf: | ||
| description: > | ||
| Measures CPU usage of a grid of images that use a FadeInImage with an |
There was a problem hiding this comment.
Measures CPU usage => Measures frame build and raster times as needsMeasureCpuGpu = false?
There was a problem hiding this comment.
Updated the langauge - I think the most important feature of this test is acutally the number of frames it pumps rather than the times. The reason I put CPU to begin with was because that stands as a proxy for CPU usage, but there's more going on for CPU usage than just building frames in the case we're trying to improve.
This reverts commit e4fbb1a.
Benchmark for #35592 and #50842
Would be ideal to land this before #50842 to measure perf impact more clearly.
I'm running this on Android under the assumption that we have more Android devices available, and there's nothing special about this particular issue to any particular platform.
I also added the macos project to macrobenchmarks because I found it helpful when locally developing the test. The test itself is all in 0fa054a