New issue
Advanced search Search tips

Issue 884288 link

Starred by 1 user
Status: WontFix
Owner:
yiyix@chromium.org
Closed: Sep 18
Cc:
npm@chromium.org
yiyix@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

13.4% regression in rendering.desktop at 590441:590498

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

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

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

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


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

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 15

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

graphic metrics: add metrics to measure SubmitCompositorFrameAfterBeginFrame by yiyix@chromium.org
https://chromium.googlesource.com/chromium/src/+/02564469c5a37896f8d46feaf283521152a55eb4
0.03466 → 0.03745 (+0.002793)

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

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

Comment 4 by yiyix@chromium.org, Sep 18 

The absolute difference is very small, only 0.002793ms. It's the time needed for recording one additional UMA metrics. 

closing the bug

Comment 5 by yiyix@chromium.org, Sep 18

Status: WontFix (was: Assigned)
►

Sign in to add a comment