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

Issue 811841 link

Starred by 1 user
Status: Fixed
Owner:
yhirano@chromium.org
Closed: Feb 2018
Cc:
yhirano@chromium.org
█ jwd@chromium.org
sullivan@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

12.7%-41.4% regression in loading.desktop at 535225:535336

Project Member Reported by sullivan@chromium.org, Feb 13 2018 
Splitting off the only linux alerts out of  bug 811336
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Feb 13 2018 

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

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


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

chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
linux-release
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Feb 14 2018

Cc: jwd@chromium.org yhirano@chromium.org
Owner: yhirano@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1180168d840000

Update RendererSideResourceScheduler testing config (Enabled_2_1024) by yhirano@chromium.org
https://chromium.googlesource.com/chromium/src/+/1f25bbc692f06964b5e10c7312f9f81377cdea32

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

Sign in to add a comment