New issue
Advanced search Search tips

Issue 889045 link

Starred by 2 users
Status: Duplicate
Owner:
jarin@chromium.org
Closed: Oct 5
Cc:
jarin@chromium.org
lanwei@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

16.4%-70.2% regression in rendering.desktop/thread_total_all_cpu_time_per_frame at 592336:592522

Project Member Reported by lanwei@chromium.org, Sep 25 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Sep 25 

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

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


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

Win 7 Nvidia GPU Perf
Win 7 Perf
mac-10_13_laptop_high_end-perf

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

Comment 3 by 42576172...@developer.gserviceaccount.com, Sep 25

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

Turn on full masking with untrusted-code-mitigations by jarin@chromium.org
https://chromium.googlesource.com/v8/v8/+/6a6f050e18b90d5b498d85455e598ca68b14238f
0.1901 → 0.2669 (+0.0768)

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

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

Comment 4 by jarin@chromium.org, Oct 5

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

Sign in to add a comment