New issue
Advanced search Search tips

Issue 920720 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

11.3% regression in blink_perf.parser at 620247:620266

Project Member Reported by majidvp@chromium.org, Jan 10

Issue description

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

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


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

Android Nexus5 Perf

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

Comment 3 by 42576172...@developer.gserviceaccount.com, Jan 19 (4 days ago)

Cc: fergal@chromium.org dgozman@chromium.org
Owner: fergal@chromium.org
Status: Assigned (was: Unconfirmed)
📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/15e12dbd940000

DocumentParser should not rely on dummy AppendBytes call by dgozman@chromium.org
https://chromium.googlesource.com/chromium/src/+/4f3f51a479aba7cd77531ad7b655abd22f92cd7a
html-parser-threaded: 5.682e+04 → 5.752e+04 (+699.7)

Revert https://crrev.com/c/1148172 to control the HTML parser yield by fergal@chromium.org
https://chromium.googlesource.com/chromium/src/+/2d7da2e9289a81e9ba92ba54af8887cdc20e7fd4
html-parser-threaded: 5.742e+04 → 6.186e+04 (+4439)

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

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

Sign in to add a comment