New issue
Advanced search Search tips

Issue 908572 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner:
Closed: Jan 9
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

5.6% regression in blink_perf.owp_storage at 608101:608168

Project Member Reported by m...@chromium.org, Nov 26

Issue description

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

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


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

mac-10_13_laptop_high_end-perf

blink_perf.owp_storage - Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks
Cc: fergal@chromium.org
Owner: fergal@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14c43f84140000

Add a testing configuration for HTMLParsingYieldTime study. by fergal@chromium.org
https://chromium.googlesource.com/chromium/src/+/e2fadf24cd0c2c40009b1eb60e38f5ff3e3c859e
Registry::RegisterBlob: 173.9 → 180.8 (+6.931)

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

Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks
Mergedinto: 905844
Status: Duplicate (was: Assigned)

Sign in to add a comment