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

Issue 886643 link

Starred by 1 user
Status: Duplicate
Merged: issue 884331
Owner:
wanderview@chromium.org
Closed: Sep 20
Cc:
wanderview@chromium.org
█ alexclarke@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

25.5% regression in blink_perf.owp_storage at 591073:591215

Project Member Reported by alexclarke@chromium.org, Sep 19 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Sep 19 

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

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


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

Win 7 Nvidia GPU Perf

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

Comment 3 by 42576172...@developer.gserviceaccount.com, Sep 20

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/100ed1a8e40000

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

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

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

Comment 4 by wanderview@chromium.org, Sep 20

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

Sign in to add a comment