New issue
Advanced search Search tips

Issue 833267 link

Starred by 1 user
Status: WontFix
Owner:
magchen@chromium.org
Closed: Apr 2018
Cc:
magchen@chromium.org
cwallez@chromium.org
isherman@chromium.org
piman@chromium.org
dcheng@chromium.org
toyoshim@chromium.org
zmo@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.1%-35.8% regression in memory.desktop at 550289:550415

Project Member Reported by toyoshim@chromium.org, Apr 16 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Apr 16 2018 

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

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


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

chromium-rel-win7-gpu-nvidia
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Apr 16 2018

Cc: zmo@chromium.org cwallez@chromium.org magchen@chromium.org isherman@chromium.org dcheng@chromium.org piman@chromium.org
Owner: magchen@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/12a0f446c40000

Adding SupportsDX12 and SupportsVulkan to UMA histogram for the Windows platform by magchen@chromium.org
https://chromium.googlesource.com/chromium/src/+/35d65e4a3183aaf2a394493288df064b444d74f8

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

Comment 7 by magchen@chromium.org, Apr 16 2018

Status: WontFix (was: Assigned)
This regression won't be fixed as it works as intended. This CL will start a GPU process to collect DX12 and Vulkan information 15 seconds after the browser launch. Then the process will quit when the job is done. The duration is short. This job needs to load D3d12.dll and vulkan-1.dll. Thus the memory consumption will increase. Both dlls will be unloaded at the end of the process.
Project Member

Comment 8 by 42576172...@developer.gserviceaccount.com, Apr 17 2018 

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14f5e536c40000

Adding SupportsDX12 and SupportsVulkan to UMA histogram for the Windows platform by magchen@chromium.org
https://chromium.googlesource.com/chromium/src/+/35d65e4a3183aaf2a394493288df064b444d74f8

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

Comment 9 by 42576172...@developer.gserviceaccount.com, Apr 17 2018 

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/149c619ac40000

Adding SupportsDX12 and SupportsVulkan to UMA histogram for the Windows platform by magchen@chromium.org
https://chromium.googlesource.com/chromium/src/+/35d65e4a3183aaf2a394493288df064b444d74f8

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

Comment 10 by 42576172...@developer.gserviceaccount.com, Apr 17 2018 

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/16e3c0bac40000

Adding SupportsDX12 and SupportsVulkan to UMA histogram for the Windows platform by magchen@chromium.org
https://chromium.googlesource.com/chromium/src/+/35d65e4a3183aaf2a394493288df064b444d74f8

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

Comment 11 by magchen@chromium.org, Apr 17 2018 

 Issue 833286  has been merged into this issue.

Comment 12 by magchen@chromium.org, Apr 17 2018 

 Issue 833277  has been merged into this issue.
►

Sign in to add a comment