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

Issue 920345 link

Starred by 1 user
Status: Assigned
Owner: ----
Cc:
█ chromium...@skia-public.iam.gserviceaccount.com
majidvp@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.4%-1.6% regression in rasterize_and_record_micro.top_25 at 619337:619338

Project Member Reported by majidvp@chromium.org, Jan 9 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jan 9 

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

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


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

linux-perf

rasterize_and_record_micro.top_25 - Benchmark documentation link:
  None
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jan 9

Cc: chromium...@skia-public.iam.gserviceaccount.com
Status: Assigned (was: Unconfirmed)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/17d504d5940000

Roll AFDO from 73.0.3657.0_rc-r1 to 73.0.3658.0_rc-r1 by chromium-autoroll@skia-public.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/8935c66cf04325e4f60d23921a52ba917dbd43b4
rasterize_time: 2.467 → 2.494 (+0.0273)

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

Benchmark documentation link:
  None
►

Sign in to add a comment