Jump to content
AIDA64 Discussion Forum
Fiery

GPU Stress Test via OpenCL GPGPU API

Recommended Posts

We've just made the new GPU stress testing feature public in the following AIDA64 beta release:

http://www.aida64.co...14gcn7wyrhdzzip

It can be used to put stress on one or more GPUs in the system, by utilizing the GPGPU computation capabilities of OpenCL API.

A couple of things to note about this new feature:

1) First of all, it is in a beta stage right now. We'd like to hear your feedbacks about it, and collect any improvement ideas. We will only roll out this new feature in an AIDA64 stable release in the first half of 2012. This feature will be disabled in any upcoming new stable releases of AIDA64 that will be rolled out in 2011.

2) Even this first public beta is capable of putting computation threads on multiple GPUs; supports CrossFireX, SLI and AMD DualGraphics configurations; supports mixed GPU configurations (one ore more nVIDIA GPUs + one or more AMD GPUs) under Windows 7; and of course it supports AMD APUs (Llano, Brazos, Trinity) as well. Putting stress simultaneously on an APU and one ore more discrete GPUs is also supported. OpenCL-capable IGP chips and mobile GPUs are supported. Multi-GPU video cards (e.g. GeForce GTX 590 and Radeon HD 6990) are supported.

3) Any OpenCL devices can be stressed, but right now it's not possible to select which devices to stress. Hence all GPU-type OpenCL devices that can be found in the system will be stressed simultaneously.

4) CPU-type OpenCL devices are not supported. We don't plan to support them, since for CPU stressing we have our own solution, the usual 64-bit System Stability Test module.

5) You can check the list of available OpenCL-capable devices on the Display / GPGPU page in AIDA64. All GPU-type devices listed there will be stressed by the AIDA64 System Stability Test.

6) Due to the way GPGPU implementations work, stressing the GPU also puts stress on other system components, e.g. system memory, CPU caches, CPU cores, and PCI Express links. Hence it's normal to have considerable CPU utilization while running the GPU stress test, even when CPU and FPU tasks are not enabled on the System Stability Test interface.

7) Due to OpenCL not being capable of providing a device utilization measurement, AIDA64 System Stability Test is not able to show the GPU load% while the stress test is running. It is however possible to check the GPU load in other places in AIDA64, e.g. on the Display / GPU page, or on the OSD Panel or SensorPanel.

8) We currently have no plans about supporting other GPGPU layers (e.g. CUDA, Stream, Direct3D CS) for GPU stressing purposes.

9) The current GPU stress module doesn't implement error-checking or results validation, hence any computation issues or glitches will not be detected or reported.

10) On old nVIDIA MCP chips (e.g. MCP73) the current GPU stress test may not work properly. We suspect it is due to a ForceWare driver bug or improper OpenCL support in ForceWare drivers. We'll investigate this issue later this year.

Please let us know what do you think about this new feature, and what improvements would you like to see about it.

Thanks,

Fiery

  • Like 1

Share this post


Link to post
Share on other sites

I did some temperature comparison between the AIDA64 module and other popular GPU stressing applications.

GPU: Two eVGA GTX460 Superclocked External Exhaust, SLI enabled.

Core @ 800 MHz

Memory @ 950 MHZ (3900 MHz effective DDR5 speed)

eVGA OCScanner v.1.7.3

1920x1200 resolution, fullscreen, heavy mode

5 minutes

GPU1 - 90°C

GPU2 - 89°C

OCCT v4.0.0

1920x1200 resolution, fullscreen, shader complexity 8,error checking on

5 minutes

GPU1 - 73°C

GPU2 - 73°C

MSI Kombustor v 1.1.3

1920x1200 resolution, fullscreen, AA off

5 minutes

GPU1 - 88°C

GPU2 - 88°C

AIDA64

5 minutes

GPU1 - 75°C

GPU2 - 75°C

Share this post


Link to post
Share on other sites

Thank you. Have you tried to check it with GPU + FPU test both enabled? I wonder how would that affect the overall system temperature and the GPU temperatures too.

Share this post


Link to post
Share on other sites

I did a comparison between eVGA OCScanner and AIDA64, same card specs as before.

eVGA OCScanner 1.7.3

1920x1200 resolution, fullscreen, heavy mode

5 minutes

GPU1 - 94°

GPU2 - 95°

AIDA64

GPU and FPU stress test enabled

5 minutes

GPU1 - 77°

GPU2 - 77°

Share this post


Link to post
Share on other sites

Thank you. Due to the fundamental difference between a full-screen 3D app and a GPGPU application (AIDA64 SST), the GPU won't be loaded or stressed the same way with those apps. On our test systems it took 15-30 minutes to make the video adapter heat up with GPGPU to the same levels that a full-screen 3D app could reach in a few minutes. It's definitely a slight issue, but since we generally recommend our users to run AIDA64 System Stability Test for at least a couple of hours, I don't think this is a show-stopper issue.

Share this post


Link to post
Share on other sites

Yes, it utilizes the general data crunching capabilities of modern GPUs rather than their ability to render high-resolution 3D images. When you "just" process a huge amount of data with the GPU, the whole video card is stressed in a different way than when running e.g. a 3D game. We picked the GPGPU way to let AIDA64 users stress their GPUs without the need to switch to full-screen mode.

Share this post


Link to post
Share on other sites

Just for a sudgestion… Put this feature in a seperate tool such as "Display Benchmark" or "Display test" or simillar. Just like the "Disk Benchmark" and "Cache and Memory Benchmark". Where all Display related test can be made and shows a graph for Temperatures, CPU Utilization, GPU Utilization, Memory Controller Utilization, Video Engine Utilization and FPS Count and gives you the ability to set the Texture Size and Vertex Count.

Share this post


Link to post
Share on other sites

Thank you. We have different plans about the System Stability Test, which involves a complete redesign of the user interface, and also to make it easier to use while retaining the current layout with improvements. Stay tuned ;)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×