New issue
Advanced search Search tips
Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Apr 18
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

5.7%-172.2% regression in thread_times.key_mobile_sites_smooth at 549274:549473

Project Member Reported by toyoshim@chromium.org, Apr 16

Issue description

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

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


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

android-nexus5X
android-nexus6
android-nexus7v2
android-webview-nexus5X
android-webview-nexus6
Cc: pdr@chromium.org wangxianzhu@chromium.org
Owner: wangxianzhu@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/16fb6e7ac40000

[SPv175+] Don't create OverflowClip if contents don't overflow by wangxianzhu@chromium.org
https://chromium.googlesource.com/chromium/src/+/62abeca8161aedf25ee126d4bc63bd3cbeac4085

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Status: WontFix (was: Assigned)
WontFix because:
- Only one test (reddit) in the suite has regressed;
- For the test, thread_GPU_cpu_time_per_frame and thread_raster_cpu_time_per_frame are only a very small part of the total frame cpu usage;
- The CL has more other benefits (memory, raster time).

Sign in to add a comment