New issue
Advanced search Search tips

Issue 911595 link

Starred by 2 users

Issue metadata

Status: Closed
Owner:
Closed: Dec 20
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

27.3% regression in rendering.desktop/thread_raster_cpu_time_per_frame at 612921:612921

Project Member Reported by toyoshim@chromium.org, Dec 4

Issue description

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

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


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

Win 7 Perf

rendering.desktop - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Owner: magchen@chromium.org
Status: Assigned (was: Untriaged)
Assigning to magchen@chromium.org because this is the only CL in range:
Force DC overlay for hardware protected video with any blend mode

For protected video, it must be protected and decoded by hardware through
Direct Composition overlay swap chain. It's fine if the blend mode is not
handled correctly.

Bug:843814

Change-Id: I07c3ed40716fd9979f3f83c395a593fa1f0b5dd5
Reviewed-on: https://chromium-review.googlesource.com/c/1357647
Reviewed-by: Sunny Sachanandani <sunnyps@chromium.org>
Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Commit-Queue: Maggie Chen <magchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612921}
I don't think the perf regression is caused by my CL. This CL is like a one liner change and it only affects protected video, which is for Windows 10 only and is NOT enabled by default yet.
😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/156ea497e40000

All of the runs failed. The most common error (20/20 runs) was:
SwarmingTestError: The test failed. No Python exception was found in the log.
😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/17ebc874140000

All of the runs failed. The most common error (20/20 runs) was:
SwarmingTestError: The test failed. No Python exception was found in the log.
Owner: ----
😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/1185b4e2140000

All of the runs failed. The most common error (20/20 runs) was:
SwarmingTestError: The test failed. No Python exception was found in the log.
😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/123ae4c2140000

All of the runs failed. The most common error (20/20 runs) was:
SwarmingTestError: The test failed. No Python exception was found in the log.
Status: Available (was: Assigned)
Owner: toyoshim@chromium.org
Status: Assigned (was: Available)
Hi toyoshim@, I think we can close this bug. If you look at the perf graph, there is no regression any more. The regression only shows for a short period of time and the current number is even better than those before the bug was opened.
Status: Closed (was: Assigned)
agreed

Sign in to add a comment