New issue
Advanced search Search tips

Issue 894890 link

Starred by 1 user
Status: Duplicate
Merged: issue 894520
Owner:
khushals...@chromium.org
Closed: Oct 13
Cc:
majidvp@google.com
khushals...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.6%-120.6% regression in rendering.mobile/tasks_per_frame_total_all at 598489:598650

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

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

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

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


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

Android Nexus5X WebView Perf
Android Nexus6 WebView Perf
android-nexus5x-perf

rendering.mobile - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Project Member

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

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

gpu: Expand oopr workaround to fallback to ES2 to all android versions. by khushalsagar@chromium.org
https://chromium.googlesource.com/chromium/src/+/332d9329983d602d6bc1f4e0b64afec2307e70ba
thread_raster_cpu_time_per_frame: 16.11 → 26.3 (+10.19)

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

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

Comment 4 by khushals...@chromium.org, Oct 13

Mergedinto: 894520
Status: Duplicate (was: Assigned)
►

Sign in to add a comment