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

Issue 830762 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: May 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

7.7%-12.5% regression in jetstream at 548736:549010

Project Member Reported by primiano@chromium.org, Apr 9 2018

Issue description

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

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


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

android-nexus5
android-nexus6
android-nexus7v2
android-webview-nexus6
chromium-rel-mac11-air
chromium-rel-mac12
chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
chromium-rel-win7-x64-dual
chromium-rel-win8-dual
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Apr 10 2018

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/13a7d974c40000
These was failing with swarming timeouts, not enough devices, retrying since we've increased capacity.
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Apr 15 2018

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/1204e382c40000
Project Member

Comment 8 by 42576172...@developer.gserviceaccount.com, Apr 25 2018

Cc: klausw@chromium.org a...@chromium.org bajones@chromium.org mstarzinger@chromium.org mlamouri@chromium.org ellyjo...@chromium.org apaci...@chromium.org kinuko@chromium.org qin...@chromium.org lazyboy@chromium.org palmer@chromium.org titzer@chromium.org xingliu@chromium.org clemensh@chromium.org
Owner: qin...@chromium.org
Status: Assigned (was: Untriaged)
📍 Found significant differences after each of 4 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/14c36699c40000

[wasm] Merge the WasmContext into WasmInstanceObject by titzer@chromium.org
https://chromium.googlesource.com/v8/v8/+/a6d974fe00df34e866abc1150294a5bbf1d42535

Report the maximum and recommended VR framebuffer resolution separately by bajones@chromium.org
https://chromium.googlesource.com/chromium/src/+/9084e42d6ea2597aed3372fa5bf4cb05b7619146

Reland "[Picture in Picture] Move generic code to content/." by apacible@chromium.org
https://chromium.googlesource.com/chromium/src/+/4f854a804a031dade96ce4b9f4660ea3423302c6

Fix an issue that download IO task runner can get cleared by qinmin@chromium.org
https://chromium.googlesource.com/chromium/src/+/89f67b0a5b9145b5a75ddc827d04f665361234a8

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Owner: titzer@chromium.org
Looks like Ben's CL ([wasm] Merge the WasmContext into WasmInstanceObject). This CL is expected to regress performance a bit, so it's probably a WontFix.
Status: Fixed (was: Assigned)
The performance seems to have recovered in the graph. It was fixed by https://chromium.googlesource.com/v8/v8/+/ff64dfa09207208d3cae0b0a0745b9397adaf9cc

Sign in to add a comment