Issue metadata
Sign in to add a comment
|
2.5% regression in memory.desktop at 585258:585302 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 23
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/10664a61640000
,
Aug 23
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/10664a61640000 Add unfold_short_circuit_as_ternary workaround by enne@chromium.org https://skia.googlesource.com/skia/+/c02165fae11402933e23ad2bb080862220b5a1a8 1.394e+08 → 1.422e+08 (+2.816e+06) Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Aug 28
bsalomon, ethannicholas: I think this bug is WontFix, because this is a correctness change. However, I'm a little surprised that this shader change resulted in a 3.4mb shader regression. Do either of you have a sense of why this might be?
,
Sep 17
I'm still curious to hear from Skia folks if they have any ideas here, but I will WontFix this for now.
,
Sep 18
I really can't imagine how it'd cause a memory regression like this. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 23