New issue
Advanced search Search tips

Issue 875827 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Aug 27
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.6%-160.1% regression in v8.browsing_mobile at 580792:581349

Project Member Reported by petermarshall@chromium.org, Aug 20

Issue description

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

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


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

Android Nexus5 Perf
android-nexus5x-perf
Cc: ksakamoto@chromium.org
Owner: ksakamoto@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1032591a640000

FMPDetector: Use network quiet signal from IdlenessDetector by ksakamoto@chromium.org
https://chromium.googlesource.com/chromium/src/+/208565993af870c86cff06c27dbc67066694bf61
20.99 → 29.95 (+8.962)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Status: WontFix (was: Assigned)
My change affects renderer's scheduling policy (the scheduler may stay in the "loading" state longer), so it may have changed the GC timings.

I think it's okay to WontFix this, considering the small number of affected benchmarks.

Sign in to add a comment