New issue
Advanced search Search tips

Issue 883826 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.4%-1.5% regression in memory.top_10_mobile at 590664:590707

Project Member Reported by npm@chromium.org, Sep 13

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=883826

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=3bdbb7546f45abba5f9f4aea1eaba5cf29a2498870e9ee01b2147b09ecf17275


Bot(s) for this bug's original alert(s):

Android Nexus5X WebView Perf

memory.top_10_mobile - Benchmark documentation link:
  None
Cc: p...@google.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/15aab8e3640000

SkRemoteGlyphCache: Make serialization code bitness agnostic. by pcc@google.com
https://skia.googlesource.com/skia/+/77b02f69f26598bd9fada225bcb22a8da47b170f
3.061e+07 → 3.096e+07 (+3.5e+05)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Benchmark documentation link:
  None
Status: Untriaged (was: Assigned)
Assigned, but no owner or component? Please find a component and/or owner

Sign in to add a comment