New issue
Advanced search Search tips

Issue 902472 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Dec 17
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

23%-484% regression in performance_browser_tests at 603959:604040

Project Member Reported by lanwei@chromium.org, Nov 6

Issue description

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

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


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

mac-10_12_laptop_low_end-perf
Cc: m...@chromium.org
Owner: m...@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/111cedf5e40000

Get performance_browser_tests working again. by miu@chromium.org
https://chromium.googlesource.com/chromium/src/+/c9cee7e5db8b778279bf39c3a249ab1140616b83
CastV2Performance_gpu_60fps: 6.758 → 18.09 (+11.33)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Status: WontFix (was: Assigned)
Part of my change was fixing the timing/analysis logic. I believe the metric change is just due to fixing that.

Sign in to add a comment