New issue
Advanced search Search tips

Issue 844575 link

Starred by 2 users
Status: WontFix
Owner:
sunn...@chromium.org
Closed: Aug 8
Cc:
sunn...@chromium.org
npm@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4.8%-28% regression in thread_times.key_silk_cases at 557779:557820

Project Member Reported by npm@chromium.org, May 18 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, May 18 2018 

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

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


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

android-nexus5
android-one
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, May 21 2018

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

Revert "Do not throttle BeginMainFrame on SubmitCompositorFrameAck" by sunnyps@chromium.org
https://chromium.googlesource.com/chromium/src/+/3d79596806759a857e72a476ecc883a650c3327d

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

Comment 4 by sullivan@chromium.org, Jul 20

Components: Speed>Metrics>SystemHealthRegressions

Comment 5 by toyoshim@chromium.org, Aug 8 

friendly ping from today's perf sheriff.
any update?

Comment 6 by sunn...@chromium.org, Aug 8

Status: WontFix (was: Assigned)
That CL was about increasing throughput for main thread which it did, and so its revert caused a regression. However, it caused regressions elsewhere, so we've shelved it for now.
►

Sign in to add a comment