Issue metadata
Sign in to add a comment
|
15.3% regression in memory.desktop at 535369:535433 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Feb 22 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14b55a2f840000
,
Feb 22 2018
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/14b55a2f840000 Move GrMakeCachedBitmapProxy work in lazy mode by egdaniel@google.com https://skia.googlesource.com/skia/+/7e1912a8ab48134eb3a631f188ad8aa262e8eaa0 Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Mar 16 2018
egdaniel: this is fixed, but any idea how?
,
Mar 16 2018
I landed this CL, https://skia-review.googlesource.com/c/skia/+/114426, which fix multiple performance regression bugs which I believe we related to memory caching issues. So not surprising that the original CL also caused a memory regression that got fixed by the same perf fix. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Feb 22 2018