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

Issue 899968 link

Starred by 1 user
Status: Untriaged
Owner: ----
Cc:
█ ushesh@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2.9%-3.4% regression in cpu_time_percentage at 601185:601361

Project Member Reported by 42576172...@developer.gserviceaccount.com, Oct 29 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Oct 29 

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

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


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

Win 7 Perf

power.desktop - Benchmark documentation link:
  https://bit.ly/power-benchmarks
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Oct 30

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

base: Bump default android version to 9.0.99 by boliu@chromium.org
https://chromium.googlesource.com/chromium/src/+/80a9405bfcb2d3c306a562ddfd8e72fd23f1a693
cpu_time_percentage: 0.0795 → 0.07005 (-0.00945)

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

Benchmark documentation link:
  https://bit.ly/power-benchmarks

Comment 4 by boliu@chromium.org, Oct 30

Cc: -boliu@chromium.org
Owner: ----
Status: Untriaged (was: Assigned)
pinpoint is wrong. android-only change cannot affect windows
►

Sign in to add a comment