New issue
Advanced search Search tips

Issue 907774 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

1.1%-63.5% regression in v8.browsing_desktop at 607128:607169

Project Member Reported by mlippautz@chromium.org, Nov 22

Issue description

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

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


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

Android Nexus5 Perf
Android Nexus5X WebView Perf
mac-10_12_laptop_low_end-perf

v8.browsing_desktop - Benchmark documentation link:
  None

v8.browsing_mobile - Benchmark documentation link:
  None

system_health.memory_mobile - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
Cc: hajimehoshi@chromium.org
Owner: hajimehoshi@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14d45880140000

mojo: Use a more appripriate task runner at HandleSignalTracker's SimpleWatch by hajimehoshi@chromium.org
https://chromium.googlesource.com/chromium/src/+/cb5a960bf9cf62fc934f8a167ac4da6219080aa2
v8-gc-incremental-step: 21.82 → 46.55 (+24.74)

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

Benchmark documentation link:
  None

Sign in to add a comment