New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 886683 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 888558
Owner: ----
Closed: Sep 24
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

8.5% regression in blink_perf.owp_storage at 592094:592146

Project Member Reported by alexclarke@chromium.org, Sep 19

Issue description

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

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


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

mac-10_12_laptop_low_end-perf
mac-10_13_laptop_high_end-perf

blink_perf.owp_storage - Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks
Cc: oysteine@google.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1072013f640000

Reland "Enable Perfetto by default for all telemetry tests" by oysteine@google.com
https://chromium.googlesource.com/chromium/src/+/0f374eff414ec0683aafbe2aae3fd405a4fcc221
54.96 → 60.35 (+5.392)

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

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

Sign in to add a comment