New issue
Advanced search Search tips

Issue 904359 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Nov 15
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

48.7% regression in v8.browsing_mobile at 606112:607097

Project Member Reported by petermarshall@google.com, Nov 12

Issue description

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

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


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

Android Nexus5 Perf

v8.browsing_mobile - Benchmark documentation link:
  None
Cc: jbudorick@chromium.org
Owner: jbudorick@chromium.org
Status: Assigned (was: Untriaged)
📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/12982253e40000

Build internal android targets in telemetry_chrome_test. by jbudorick@chromium.org
https://chromium.googlesource.com/chromium/src/+/e0c7bc0e869c70995d8b53d9a22e68294f07c7f2
v8-gc-scavenger: 22.69 → No values

Revert "Build internal android targets in telemetry_chrome_test." by jbudorick@chromium.org
https://chromium.googlesource.com/chromium/src/+/c7539ef6291836eff22077b38ae55bb62f536b99
v8-gc-scavenger: No values → 35.12

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

Benchmark documentation link:
  None
Status: WontFix (was: Assigned)
Noise & build failures, nevermind

Sign in to add a comment