New issue
Advanced search Search tips

Issue 920372 link

Starred by 1 user
Status: Duplicate
Merged: issue 917259
Owner:
carlscab@google.com
Closed: Jan 15
Cc:
carlscab@google.com
majidvp@google.com
lfg@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

21.9% regression in blink_perf.bindings at 616638:616897

Project Member Reported by majidvp@chromium.org, Jan 9 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jan 9 

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=920372

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


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

mac-10_12_laptop_low_end-perf

blink_perf.bindings - Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jan 10

Cc: carlscab@google.com
Owner: carlscab@google.com
Status: Assigned (was: Unconfirmed)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/175ab251940000

Add SequenceManager to field trial testing config by carlscab@google.com
https://chromium.googlesource.com/chromium/src/+/84ecbf7c0b1eca668dba1471a50f065c6d558737
post-message: 293.9 → 367.6 (+73.69)

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

Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks

Comment 4 by carlscab@google.com, Jan 15

Mergedinto: 917259
Status: Duplicate (was: Assigned)
►

Sign in to add a comment