New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 770376 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jul 11
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug

Blocked on:
issue 688558



Sign in to add a comment

Intel and Nvidia perf bots using software compositing

Project Member Reported by sullivan@chromium.org, Sep 29 2017

Issue description

Split off from https://bugs.chromium.org/p/chromium/issues/detail?id=755286#c16:

> perf bots run not just with software rasterization, but also with software compositing (a surprise to us) - e.g.
> 
> https://chromium-swarm.appspot.com/task?id=38c254de1c034b10&refresh=10&show_raw=1
> 
> (INFO) 2017-09-22 07:05:42,275 browser._LogBrowserInfo:138  Feature Status:
> (INFO) 2017-09-22 07:05:42,275 browser._LogBrowserInfo:140    2d_canvas           : unavailable_software
> (INFO) 2017-09-22 07:05:42,275 browser._LogBrowserInfo:140    checker_imaging     : disabled_off
> (INFO) 2017-09-22 07:05:42,275 browser._LogBrowserInfo:140    flash_3d            : unavailable_software
> (INFO) 2017-09-22 07:05:42,275 browser._LogBrowserInfo:140    flash_stage3d       : unavailable_software
> (INFO) 2017-09-22 07:05:42,275 browser._LogBrowserInfo:140    flash_stage3d_baseline: unavailable_software
> (INFO) 2017-09-22 07:05:42,275 browser._LogBrowserInfo:140    gpu_compositing     : unavailable_software
> (INFO) 2017-09-22 07:05:42,275 browser._LogBrowserInfo:140    multiple_raster_threads: enabled_on
> (INFO) 2017-09-22 07:05:42,275 browser._LogBrowserInfo:140    native_gpu_memory_buffers: disabled_software
> (INFO) 2017-09-22 07:05:42,275 browser._LogBrowserInfo:140    rasterization       : unavailable_software
> (INFO) 2017-09-22 07:05:42,275 browser._LogBrowserInfo:140    video_decode        : unavailable_software
> (INFO) 2017-09-22 07:05:42,275 browser._LogBrowserInfo:140    video_encode        : unavailable_software
> (INFO) 2017-09-22 07:05:42,275 browser._LogBrowserInfo:140    webgl               : enabled_readback
> (INFO) 2017-09-22 07:05:42,275 browser._LogBrowserInfo:140    webgl2              : unavailable_off

There are actually a bunch of windows perfbots. The standard windows config was set up many years ago with more of a server config before we really thought to do GPU testing. These bots have that server config:
chromium-rel-win7-dual
chromium-rel-win7-x64-dual
chromium-rel-win8-dual
chromium-rel-win10

But the following windows bots should be doing GPU compositing:
win-high-dpi
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia

Looking at the graphs for all the windows bots around the time of the software compositing regression in bug 755286, we see that 
chromium-rel-win7-gpu-intel and chromium-rel-win7-gpu-nvidia exhibit this regression:
https://chromeperf.appspot.com/report?sid=31685d55df80afcb906503ac77809e63fa498986cc92b6e5dfb440a5c2f4baa7&rev=500113

And indeed, if you look at the logs, you see:


win-high-dpi
https://chromium-swarm.appspot.com/user/task/38cc5d9502c1d510
Intel(R) HD Graphics 5500
...
(INFO) 2017-09-24 05:57:46,493 browser._LogBrowserInfo:138  Feature Status:
(INFO) 2017-09-24 05:57:46,493 browser._LogBrowserInfo:140    2d_canvas           : enabled
(INFO) 2017-09-24 05:57:46,493 browser._LogBrowserInfo:140    checker_imaging     : enabled_on
(INFO) 2017-09-24 05:57:46,493 browser._LogBrowserInfo:140    flash_3d            : enabled
(INFO) 2017-09-24 05:57:46,493 browser._LogBrowserInfo:140    flash_stage3d       : enabled
(INFO) 2017-09-24 05:57:46,493 browser._LogBrowserInfo:140    flash_stage3d_baseline: enabled
(INFO) 2017-09-24 05:57:46,493 browser._LogBrowserInfo:140    gpu_compositing     : enabled
(INFO) 2017-09-24 05:57:46,493 browser._LogBrowserInfo:140    multiple_raster_threads: enabled_on
(INFO) 2017-09-24 05:57:46,493 browser._LogBrowserInfo:140    native_gpu_memory_buffers: disabled_software
(INFO) 2017-09-24 05:57:46,494 browser._LogBrowserInfo:140    rasterization       : enabled
(INFO) 2017-09-24 05:57:46,494 browser._LogBrowserInfo:140    video_decode        : enabled
(INFO) 2017-09-24 05:57:46,494 browser._LogBrowserInfo:140    video_encode        : enabled
(INFO) 2017-09-24 05:57:46,494 browser._LogBrowserInfo:140    webgl               : enabled
(INFO) 2017-09-24 05:57:46,494 browser._LogBrowserInfo:140    webgl2              : enabled


chromium-rel-win7-gpu-ati
https://chromium-swarm.appspot.com/user/task/38c6ab5b8aa3ea10
AMD Radeon R7 200 Series Direct3D11
....
(INFO) 2017-09-23 03:00:46,193 browser._LogBrowserInfo:138  Feature Status:
(INFO) 2017-09-23 03:00:46,194 browser._LogBrowserInfo:140    2d_canvas           : enabled
(INFO) 2017-09-23 03:00:46,194 browser._LogBrowserInfo:140    checker_imaging     : enabled_on
(INFO) 2017-09-23 03:00:46,194 browser._LogBrowserInfo:140    flash_3d            : enabled
(INFO) 2017-09-23 03:00:46,194 browser._LogBrowserInfo:140    flash_stage3d       : enabled
(INFO) 2017-09-23 03:00:46,194 browser._LogBrowserInfo:140    flash_stage3d_baseline: enabled
(INFO) 2017-09-23 03:00:46,194 browser._LogBrowserInfo:140    gpu_compositing     : enabled
(INFO) 2017-09-23 03:00:46,194 browser._LogBrowserInfo:140    multiple_raster_threads: enabled_on
(INFO) 2017-09-23 03:00:46,194 browser._LogBrowserInfo:140    native_gpu_memory_buffers: disabled_software
(INFO) 2017-09-23 03:00:46,194 browser._LogBrowserInfo:140    rasterization       : unavailable_software
(INFO) 2017-09-23 03:00:46,194 browser._LogBrowserInfo:140    video_decode        : enabled
(INFO) 2017-09-23 03:00:46,194 browser._LogBrowserInfo:140    video_encode        : enabled
(INFO) 2017-09-23 03:00:46,194 browser._LogBrowserInfo:140    webgl               : enabled
(INFO) 2017-09-23 03:00:46,194 browser._LogBrowserInfo:140    webgl2              : enabled


chromium-rel-win7-gpu-intel
https://chromium-swarm.appspot.com/user/task/38be301849b8c610
(INFO) 2017-09-21 11:22:59,224 browser._LogBrowserInfo:138  Feature Status:
(INFO) 2017-09-21 11:22:59,226 browser._LogBrowserInfo:140    2d_canvas           : unavailable_software
(INFO) 2017-09-21 11:22:59,226 browser._LogBrowserInfo:140    checker_imaging     : enabled_on
(INFO) 2017-09-21 11:22:59,226 browser._LogBrowserInfo:140    flash_3d            : unavailable_software
(INFO) 2017-09-21 11:22:59,226 browser._LogBrowserInfo:140    flash_stage3d       : unavailable_software
(INFO) 2017-09-21 11:22:59,226 browser._LogBrowserInfo:140    flash_stage3d_baseline: unavailable_software
(INFO) 2017-09-21 11:22:59,226 browser._LogBrowserInfo:140    gpu_compositing     : unavailable_software
(INFO) 2017-09-21 11:22:59,226 browser._LogBrowserInfo:140    multiple_raster_threads: enabled_on
(INFO) 2017-09-21 11:22:59,226 browser._LogBrowserInfo:140    native_gpu_memory_buffers: disabled_software
(INFO) 2017-09-21 11:22:59,226 browser._LogBrowserInfo:140    rasterization       : unavailable_software
(INFO) 2017-09-21 11:22:59,226 browser._LogBrowserInfo:140    video_decode        : unavailable_software
(INFO) 2017-09-21 11:22:59,226 browser._LogBrowserInfo:140    video_encode        : unavailable_software
(INFO) 2017-09-21 11:22:59,226 browser._LogBrowserInfo:140    webgl               : enabled_readback
(INFO) 2017-09-21 11:22:59,226 browser._LogBrowserInfo:140    webgl2              : enabled_readback


chromium-rel-win7-gpu-nvidia
https://chromium-swarm.appspot.com/user/task/38d472aeb9400310
(INFO) 2017-09-25 19:07:39,497 browser._LogBrowserInfo:138  Feature Status:
(INFO) 2017-09-25 19:07:39,497 browser._LogBrowserInfo:140    2d_canvas           : enabled
(INFO) 2017-09-25 19:07:39,497 browser._LogBrowserInfo:140    checker_imaging     : enabled_on
(INFO) 2017-09-25 19:07:39,497 browser._LogBrowserInfo:140    flash_3d            : enabled
(INFO) 2017-09-25 19:07:39,497 browser._LogBrowserInfo:140    flash_stage3d       : enabled
(INFO) 2017-09-25 19:07:39,497 browser._LogBrowserInfo:140    flash_stage3d_baseline: enabled
(INFO) 2017-09-25 19:07:39,497 browser._LogBrowserInfo:140    gpu_compositing     : enabled
(INFO) 2017-09-25 19:07:39,497 browser._LogBrowserInfo:140    multiple_raster_threads: enabled_on
(INFO) 2017-09-25 19:07:39,497 browser._LogBrowserInfo:140    native_gpu_memory_buffers: disabled_software
(INFO) 2017-09-25 19:07:39,497 browser._LogBrowserInfo:140    rasterization       : unavailable_software
(INFO) 2017-09-25 19:07:39,497 browser._LogBrowserInfo:140    video_decode        : enabled
(INFO) 2017-09-25 19:07:39,497 browser._LogBrowserInfo:140    video_encode        : enabled
(INFO) 2017-09-25 19:07:39,497 browser._LogBrowserInfo:140    webgl               : enabled
(INFO) 2017-09-25 19:07:39,497 browser._LogBrowserInfo:140    webgl2              : enabled

The Intel GPU bot is a known issue ( bug 688558 ) and we still have some intel coverage on win-high-dpi. But AFAIK the Nvidia was not a known issue. Short term, let's see if we can fix it. Long-term, benchmarking team is looking at revamping our hardware configs in 2018.

Vince, can triage for someone to check the KVM on the Nvidia bots? They are build9{2..6}-m1? The bot this test ran on was build96-m1 so something is definitely not right there.
 

Comment 1 by vhang@chromium.org, Sep 30 2017

These bots are in Atlanta.  Do you need someone to physically check on the KVM connection on these Nvidia bots or have someone remotely log in to do some troubleshooting?
Cc: kbr@chromium.org
I believe Annie wanted "someone to physically check on the KVM connection on these Nvidia bots"
The list of bots we want you to check:
Win 8 Perf: 'build143-m1', 'build144-m1', build145-m1', 'build146-m1', 'build147-m1'
Win 7 Nvidia GPU Perf: 'build101-m1', 'build102-m1', 'build103-m1', 'build104-m1', 'build105-m1'
Win 7 Intel GPU Perf: 'build164-m1', 'build165-m1',  'build166-m1', 'build167-m1', 'build168-m1'
Win 7 Perf: 'build185-m1', 'build186-m1', 'build187-m1', 'build188-m1', 'build189-m1'
Win 7 x64 Perf: 'build138-m1', 'build139-m1', 'build140-m1', 'build141-m1', 'build142-m1'
Win 7 ATI GPU Perf: 'build101-m1', 'build102-m1', 'build103-m1', 'build104-m1', 'build105-m1'

Request:
We want to check whether the KVM connections on these bots are loose, and whether the drivers are working.

Comment 4 by d...@chromium.org, Oct 2 2017

The issue is not with the KVM connection, I checked those remotely. 

This sounds more like the tests are not ignoring the on-board video controller (Matrox based) which exists on the Nvidia/AMD machines and is running its tests there, nevermind the default video output is set to the add-in GPU.

kbr@ might have more to add on how their tests ignore that GPU.

Comment 5 by kbr@chromium.org, Oct 2 2017

Cc: ericrk@chromium.org
The NVIDIA bot seems to have GPU rasterization disabled because of this blacklist entry #136:
https://chromium.googlesource.com/chromium/src/+/master/gpu/config/software_rendering_list.json#1342

That doesn't seem to be a new regression. It's using GPU compositing per the logs above.

The only bot in the list above that seems to be misconfigured is the Intel GPU bot.

The GPU correctness tests don't do anything special to ignore the Matrox GPU. On machines where it was interfering with correct operation of Chrome we asked the Labs team to disable it at the BIOS level. But on Windows we found at some point that the Matrox GPU didn't have any adverse effect so we haven't been asking for it to be disabled on recently installed machines.

Comment 6 by d...@chromium.org, Oct 2 2017

> On machines where it was interfering with correct operation of Chrome we asked the Labs team to disable it at the BIOS level.

I'm going to point out this is done for _any machine which uses an add-in video card_. It's not an optional thing, it's the standard configuration otherwise the add-in card is not used properly.

Comment 7 by kbr@chromium.org, Oct 2 2017

Please see this bot list:
https://chromium-swarm.appspot.com/botlist?c=id&c=os&c=task&c=status&c=gpu&c=pool&f=gpu%3ANVIDIA%20GeForce%20GT%20610%20(10de%3A104a)&f=pool%3AChrome-GPU&l=100&s=id%3Aasc

In the Chrome-GPU pool, most or all of the Windows bots still report the presence of the Matrox GPU, and they're functioning as expected.

Doing a quick inventory.  

Win 8 Perf: 'build143-m1', 'build144-m1', build145-m1', 'build146-m1', 'build147-m1'
These are all legacy r210 with only embedded matrox gpu.  MS's basic video driver is being used.  We could install the native matrox driver on these?

Win 7 Nvidia GPU Perf: 'build101-m1', 'build102-m1', 'build103-m1', 'build104-m1', 'build105-m1'
You must mean other hosts.  These are ati based r220's.  


Win 7 Intel GPU Perf: 'build164-m1', 'build165-m1',  'build166-m1', 'build167-m1', 'build168-m1'   
These are the Xeon based P4600 embedded gpu's.  kbr went away from these and onto desktop i7 based for testing on Intel gpus.  You may want to do the same?

Win 7 Perf: 'build185-m1', 'build186-m1', 'build187-m1', 'build188-m1', 'build189-m1'
These also are legacy r210 with only embedded matrox gpu

Win 7 x64 Perf: 'build138-m1', 'build139-m1', 'build140-m1', 'build141-m1', 'build142-m1'
Also r210's with only embedded matrox gpu

Win 7 ATI GPU Perf: 'build101-m1', 'build102-m1', 'build103-m1', 'build104-m1', 'build105-m1'
These are r220's with ATI r7 based gpu's.





Comment 9 by kbr@chromium.org, Oct 2 2017

Note - I'd fully support using one unified pool of Swarming hosts for both Perf testing and GPU correctness testing, to minimize the number of hardware configurations.

I'd also support that if it means we can benefit from improvements kbr@ and team make to a pool of bots.
Filed  issue 771597  to add flag that enables asserting GPU rendering.

Comment 12 by vhang@chromium.org, Nov 13 2017

Status: Assigned (was: Untriaged)
All these bots were recently upgraded with the Nvidia p400 GPU.  Are you still having issues with them?
Cc: sadrul@chromium.org
Status: Fixed (was: Assigned)
Please reopen if this is still an issue.  Thanks

Sign in to add a comment