New issue
Advanced search Search tips

Issue 891256 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Oct 23
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.5% regression in rendering.mobile/thread_total_all_cpu_time_per_frame at 594393:594468

Project Member Reported by tdres...@chromium.org, Oct 2

Issue description

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

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


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

android-nexus5x-perf

rendering.mobile - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Cc: torne@google.com thomasanderson@chromium.org
Owner: thomasanderson@chromium.org
Status: Assigned (was: Untriaged)
📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/145cb828e40000

Define basic Trichrome build targets. by torne@google.com
https://chromium.googlesource.com/chromium/src/+/bef92b9197b49def215aced79961f50e3b83544e
18.86 → No values

Revert "Define basic Trichrome build targets." by thomasanderson@chromium.org
https://chromium.googlesource.com/chromium/src/+/f505cde61a75f566b4edd2043015a93e5568f970
No values → 19.52

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

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Cc: -thomasanderson@chromium.org
Owner: torne@chromium.org
Status: WontFix (was: Assigned)
Looks like just mostly noise to me.

Sign in to add a comment