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

Issue 830826 link

Starred by 1 user
Status: WontFix
Owner:
chcunningham@chromium.org
Closed: Apr 2018
Cc:
█ pdyson@chromium.org
martis@chromium.org
jamiewa...@chromium.org
jiameng@chromium.org
chcunningham@chromium.org
michae...@chromium.org
█ holte@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

12.8% regression in media.desktop at 548277:548355

Project Member Reported by chcunningham@chromium.org, Apr 9 2018 
No ref graph. Metric is bouncing around quite a bit, though it seems to be on average still higher than previous values.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Apr 9 2018 

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

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


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

chromium-rel-win7-gpu-intel
Project Member

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

Cc: martis@chromium.org derat@chromium.org michae...@chromium.org holte@chromium.org boliu@chromium.org yuweih@chromium.org pdyson@chromium.org jinsuk...@chromium.org jiameng@chromium.org jamiewa...@chromium.org
Owner: yuweih@chromium.org
Status: Assigned (was: Untriaged)
📍 Found significant differences after each of 3 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/12998bacc40000

Android: Fix assertion failure in RWHVA destruction by jinsukkim@chromium.org
https://chromium.googlesource.com/chromium/src/+/89a2cd44df428826a736dd8540687fcf481504de

Ukm logging for the Screen Brightness project. by pdyson@chromium.org
https://chromium.googlesource.com/chromium/src/+/6a8222922cd8ceaee8bcc7140160a5a0ff41b318

Disable PORTALLOCATOR_DISABLE_COSTLY_NETWORKS by yuweih@chromium.org
https://chromium.googlesource.com/chromium/src/+/254ce1becd1721b163a8014cc9a9e5b6893a57b6

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

Comment 4 by derat@chromium.org, Apr 10 2018

Cc: -derat@chromium.org
6a8222922cd8ceaee8bcc7140160a5a0ff41b318 was Chrome-OS-only and couldn't have caused a regression on Win7.

Comment 5 by yuweih@chromium.org, Apr 10 2018

Cc: -yuweih@chromium.org
Owner: chcunningham@chromium.org
254ce1becd1721b163a8014cc9a9e5b6893a57b6 only affects Chrome Remote Desktop and doesn't affect Chrome.

Comment 6 by pdyson@chromium.org, Apr 10 2018 

6a8222922cd8ceaee8bcc7140160a5a0ff41b318 is not called yet by other code so couldn't affect memory.

Comment 7 by jinsuk...@chromium.org, Apr 10 2018

Cc: -jinsuk...@chromium.org -boliu@chromium.org
89a2cd44df428826a736dd8540687fcf481504de affects Android only.

Comment 8 by chcunningham@chromium.org, Apr 10 2018

Status: WontFix (was: Assigned)
Looking at latest points in the graph, looks like it regularly bounces back into the pre-regression range, so this is probably just noise.
bouncy_graph.png
22.6 KB View Download
►

Sign in to add a comment