New issue
Advanced search Search tips

Issue 921256 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jan 14
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.6% regression in speedometer at 621849:622000

Project Member Reported by m...@chromium.org, Jan 12

Issue description

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

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


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

Android Nexus6 WebView Perf

speedometer - Benchmark documentation link:
  None
Cc: harringtond@google.com timvolod...@chromium.org
Owner: timvolod...@chromium.org
Status: Assigned (was: Unconfirmed)
📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/118d7afb940000

Track when the auto-fetch in progress notification should be shown by harringtond@google.com
https://chromium.googlesource.com/chromium/src/+/0b15d057e7dacd7e14d2ff3b0308c1cc2b706695
Total: 6.104e+04 → No values

Revert "Track when the auto-fetch in progress notification should be shown" by timvolodine@chromium.org
https://chromium.googlesource.com/chromium/src/+/dd6d6cf97b6a95c258cb7deb49b6a3ead32ddad1
Total: No values → 6.354e+04

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

Benchmark documentation link:
  None
looking at the pinpoint, it seems to point at the red patch:
https://chromium-review.googlesource.com/c/chromium/src/+/1381233

which was reverted later.

It also looks like the overall graph [1] has normalized since then..

[1] https://chromeperf.appspot.com/group_report?bug_id=921256

Cc: -harringtond@google.com
Owner: harringtond@google.com
reassigning to harringtond@google.com (as the author of the patch) (not sure if the patch was relanded since then).

But it looks like this bug can be closed.
Status: Fixed (was: Assigned)
Cc: harringtond@google.com
📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/11df7b28540000

Track when the auto-fetch in progress notification should be shown by harringtond@google.com
https://chromium.googlesource.com/chromium/src/+/0b15d057e7dacd7e14d2ff3b0308c1cc2b706695
Total: 6.092e+04 → No values

Revert "Track when the auto-fetch in progress notification should be shown" by timvolodine@chromium.org
https://chromium.googlesource.com/chromium/src/+/dd6d6cf97b6a95c258cb7deb49b6a3ead32ddad1
Total: No values → 6.359e+04

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

Benchmark documentation link:
  None

Sign in to add a comment