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

Issue 887287 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

23.2% regression in blink_perf.owp_storage at 591048:591241

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

Issue description

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

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


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

Win 7 Perf

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

Tune the mojo::DataPipe capacity and read chunk size when reading blobs. by wanderview@chromium.org
https://chromium.googlesource.com/chromium/src/+/25b9a8e66efcad49b254d4c0a1b09cb9a9c8a6b8
737.1 → 843.5 (+106.4)

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

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

Sign in to add a comment