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

Issue 886673 link

Starred by 1 user
Status: WontFix
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

5.5% regression in blink_perf.owp_storage at 591820:591903

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=886673

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


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

Android Nexus5 Perf
Android Nexus6 WebView 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/111dd7c0e40000

Use exact size for mojo::DataPipes when reading smaller blobs. by wanderview@chromium.org
https://chromium.googlesource.com/chromium/src/+/130518b367014dade21c360afd6bf50986fb4f79
3490 → 3656 (+166.3)

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

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

Comment 4 by wanderview@chromium.org, Sep 20

Status: WontFix (was: Assigned)
This is another small regression in a microbenchmark.  Since avoiding over-allocation of shared memory has larger system-wide benefits I'm going to mark this as WONTFIX, similar to  bug 884331 .
►

Sign in to add a comment