What is New in HeavyLoad?

• More languages for the user interface: The UI is now available in several additional languages. We would like to thank all of our translators who have contributed to making this possible!
• The intervals in which HeavyLoad stresses the system are now highlighted in the graph.
• You can now run all stress tests at once using maximum settings with the new so called “Maximum Terror Button”.
• A memory leak while executing the GPU-Test was fixed and overall memory consumption has been lowered.

05/02/2023

• HeavyLoad now supports to put systems with more than 64 logical processors to full load.
• A problem with starting the GPU test from the command line has been fixed.

10/25/2022

• It is now possible to select one or more GPUs for the stress test.
• The GPU stress test has been improved and now generates significantly more load on the selected graphics boards.
• Support for Windows versions prior to Windows 8.1 has been discontinued with this release.

01/25/2022

Improvements

• Running on a virtual machine, HeavyLoad now explicitly indicates that there is a risk of overloading the machine's host.
• The CPU test now supports the load of more than 32 processor cores.
• HeavyLoad can now also be executed in the background using the command line option "/NoGui".
• HeavyLoad is now also available via Chocolatey.

Bugfixes:

• Settings in the checkboxes of the diagram legend are now persistent even after a new installation.
• Fields that do not support negative values now ignore the entry of "-".

• An occasional floating point overflow in graphic drivers was fixed.
• Limiting the available memory to more than 2GB was ignored previously. This is fixed now.

04/10/2019

Improvements

• The user interface looks more modern now.
• Better support of high DPI scaled monitors.
• For better readability size values of files or memory are shown in the most appropriate dimension (KB, MB, GB) now.
• The memory stress test was improved. HeavyLoad now uses the available memory, thus allowing a higher load.
• Instead of showing the free memory, the status bar shows the amount of available memory now.

Bug fixes

If you forget to specify a test method when starting the test routine via command line, HeavyLoad warns you and the /AUTOEXIT parameter terminates HeavyLoad quickly in that case now.

02/19/2019

• Please note: Windows XP and Server 2003 are no longer supported.
• Bugfix: The test method "Stress GPU" was unable to load textures to produce GPU utilization with current OpenGL drivers. The component used to produce the textures has been updated.
• Bugfix: Under Windows 10 individual CPU cores could not be utilized separately. This error has been fixed. The load threads allocated now explicitly individual CPU cores.
• Bugfix: The base load of HeavyLoad (when running without active tests) could be reduced to less than 5%. The load was caused by the calculation of real free memory in the StatusBar.
• The "Simulate Disc Access" test now uses the latest version of TreeSize Free (v3.4.5).
• A few minor fixes have been incorporated.

08/22/2016

• The "Simulate Disc Access" test now uses the latest version of TreeSize Free (V3.0.1).
• Bugfix: An error occurring when HeavyLoad was started with GPU stress test via command line has been fixed.
• Bugfix: A representation error of the shortcuts in the options dialog occurring when the Windows classic theme was used has been fixed.
• A few minor fixes have been incorporated.

04/15/2014

• The test method "Allocate Memory" has been revised. HeavyLoad will now hold the threshold much more stable than before.
• HeavyLoad is now also available as a native 64-bit application. RAM values greater than 2 GB can now be allocated.
• Usability improvement: Options can now be controlled via shortcuts.
• Portable version: The test file will no longer be saved to a non-existing path.
• The "Simulate Disc Access" test now uses the latest version of TreeSize Free (V2.7).
• Bugfix (Portable Version): An error occurring when switching to a system with fewer CPU cores has been fixed.
• A few minor fixes have been incorporated.

11/26/2013