2025 GPU Computing Guide for CST Suite
2025 GPU Computing Guide for CST Suite
Contents
1 Nomenclature 4
2 Supported Hardware 5
2.1 Supported Solvers and Features for NVIDIA GPUs . . . . . . . . . . . . . . . 5
2.2 Supported Solvers and Features for AMD GPUs . . . . . . . . . . . . . . . . 6
4 Licensing 6
[Link]/SIMULIA c Dassault Systèmes GPU Computing Guide 2025
6 List of supported NVIDIA GPU hardware for CST Studio Suite 2025 7
7 List of deprecated NVIDIA GPU hardware for CST Studio Suite 2025 11
14 List of supported AMD GPU hardware for CST Studio Suite 2025 31
14.1 Supported GPUs: General information . . . . . . . . . . . . . . . . . . . . . . 32
14.2 Supported GPUs: Specifications . . . . . . . . . . . . . . . . . . . . . . . . . 32
17 History of Changes 34
[Link]/SIMULIA c Dassault Systèmes GPU Computing Guide 2025
4
1 Nomenclature
The following section explains the nomenclature used in this document.
<...> Within commands the sections you should replace according to your
environment are enclosed in "<...>". For example "<CST_DIR>"
should be replaced by the directory where you have installed CST
Studio Suite (e.g. "c:\Program Files\CST Studio Suite").
[Link]/SIMULIA c Dassault Systèmes GPU Computing Guide 2025
5
2 Supported Hardware
CST Studio Suite supports Hardware Acceleration for various Solvers and GPUs. In combi-
nation with NVIDIA GPUs many different kind of Solvers and GPUs are supported. Please
check the tables below for more details.
Starting with CST Studio Suite 2021 also selected AMD GPUs are supported to accelerate
the Time Domain Solver only. For more information please contact our local 3DS/SIMULIA
support team ([Link]
CST Studio Suite currently supports up to 16 GPU devices in a single host system, meaning
each number of GPU devices between 1 and 16 is supported.1
[Link]/SIMULIA c Dassault Systèmes GPU Computing Guide 2025
• Particle-In-Cell (PIC-solver)
[Link]
In general, GPU computing can be used on any of the supported operating systems.
4 Licensing
The GPU computing feature is licensed either by Acceleration Tokens with CST Studio Suite
License Model or by SimUnit tokens or credits with the SIMULIA Unified License model.
I.e. your license must contain a sufficient amount of Acceleration Tokens or SimUnit to-
kens/credits, depending on the used hardware configuration and license model, if you want
to accelerate your simulations by using a GPU. Please contact your Dassault Systèmes sales
representative for further information.
3. Switch on "Hardware acceleration" and specify how many GPU devices should be
used for this simulation. The specification of the number of devices is per solver (e.g.
if DC is used). Please note that the maximum number of GPU devices available for a
simulation depends upon the number of tokens in your license.
[Link]/SIMULIA c Dassault Systèmes GPU Computing Guide 2025
In Windows:
In Linux:
[Link]
2
This example shows the batch mode simulation for the transient solver (-m -r). To learn more about the
command line switches used by CST Studio Suite please refer to the online help documentation in the section
‘General Features’, subsection ‘Command Line Options’.
8
• Please note that a 64 bit computer architecture is required for GPU Computing.
• CST Studio Suite officially supports the NVIDIA Tesla and Quadro cards listed in the
table below. That means that these GPUs are well tested and validated with CST
software and you can contact CST support in case you run into any problems.
• Please note that cards of different generations (e.g. "Ampere" and "Volta") can’t be
combined in a single host system for GPU Computing.
• Platform = Servers: These GPUs are only available with a passive cooling system
which only provides sufficient cooling if it’s used in combination with additional fans.
These fans are usually available for server chassis only!
[Link]/SIMULIA c Dassault Systèmes GPU Computing Guide 2025
• Platform = Workstations: These GPUs provide active cooling, so they are suitable for
workstation computer chassis as well.
• GPUs with reduced FP64 performance (e.g. GPUs where the FP64 performance is
less than half the speed of the FP32 performance) are not well suited for solvers which
require a high FP64 performance. Pease check chapter 2 Supported Hardware for
affected solvers.
• Memory and problem size: For the Time Domain Solver (FIT) the rule of thumb is
"available memory divided by 100" (e.g. a GPU with 16 GB of Memory will be sufficient
for a simulation with 160 million meshcells. The memory consumption is dependent on
the used features, so the maximum simulation size might be more or less than that).
9
3
Important: GPU device with reduced double precision performance; please check chapter 2
Supported Hardware for affected solvers.
10
The NVIDIA GPUs that fulfill the following requirements may be enabled for simulations:
The recommended drivers will work for all supported Tesla and Quadro GPUs. For Quadro
GPUs: Please check the NVIDIA Driver website for a similar Tesla GPU (same generation,
e.g. Ada or Hopper) to be able to find the recommended driver. If you select a different driver
version please make sure that the driver fullfills the minimum requirement for the CUDA
compute capability of 12.4. In case there is no driver available which matches the minimum
CUDA compatibility of 12.4 please install a driver with at least CUDA 12.X compatibility: In
that case the GPU will use the Nvidia compatibility mode. This setup is rarely tested on our
side, so it is considered an unverified setup.
After you have downloaded the installer executable please start the installation procedure
by double clicking on the installer executable. After a quick series of pop-up windows, the
NVIDIA InstallShield Wizard will appear. Press the "Next" button and driver installation will
begin (The screen may turn black momentarily.). You may receive a message indicating that
the hardware has not passed Windows logo testing. In case you get this warning select
"Continue Anyway".
If you are updating from a previously installed NVIDIA driver, it’s recommended to select
"clean installation" in the NVIDIA Installshield Wizard. This will remove the current driver
prior to installing the new driver.
The "Wizard Complete" window will appear as soon as the installation has finished. Select
"Yes, I want to restart my computer now" and click the "Finish" button.
It is recommended that you run the HWAccDiagnostics tool after the installation to
confirm that the driver has been successfully installed. Please use HWAccDiagnos-
tics_AMD64.exe which can be found in the AMD64 directory of the installation folder.
14
2. Make sure that the adapter has been recognized by the system using the command
/sbin/lspci | grep -i nvidia
If you do not see any settings try to update the PCI hardware database of your system
using the command
/sbin/update-pciids
3. Stop the X-Server by running in a terminal the command (You may skip this step if you
are working on a system without X-server)
[Link]/SIMULIA c Dassault Systèmes GPU Computing Guide 2025
init 3
(on systems using SysVinit)
4. Install the NVIDIA graphics driver. Follow the instructions of the setup script. In most
cases the installer needs to compile a specific kernel module. If this is the case the
gcc compiler and Linux kernel headers need to be available on the machine.
5. Restart the X-server by running the command (You may skip this step if you are work-
ing on a system without X-server)
init 5
(on systems using SysVinit)
Note: In case you’re using the CST Distributed Computing system and a DC Solver
Server is running on the machine where you just installed the driver you need to restart
the DC Solver Server as otherwise the GPUs cannot be detected properly.
Note: The OpenGL libraries should not be installed on a system which has no ren-
dering capabilities (like a pure DC Solver Server or a pure cluster node). This can be
accomplished by starting the NVIDIA installer using the option "–no-opengl-files".
15
6. You may skip this step if a X-server is installed on your system and you are using a
NVIDIA graphics adapter (in addition to the GPU Computing devices) in your system.
If no X-server is installed on your machine or you don’t have an additional NVIDIA
graphics adapter, the NVIDIA kernel module will not be loaded automatically. Addition-
ally, the device files for the GPUs will not be generated automatically. The following
commands will perform the necessary steps to use the hardware for GPU Computing.
It is recommended to append this code to your [Link] file such that it is executed
automatically during system start.
fi
Please note:
• If you encounter problems during restart of the X-server please check chapter 8 "Com-
mon Problems" in the file [Link] located at
/usr/share/doc/NVIDIA_GLX-1.0. Please also consider removing existing sound
cards or deactivating onboard sound in the BIOS. Furthermore, make sure you are
running the latest BIOS version.
• After installation, if the X system reports an error like no screen found, please check
Xorg log files in /var/log. Open the log files in an editor and search for "PCI". Accord-
ing to the number of hardware cards in your system you will find entries of the following
form: PCI: (0@7:0:0). In /etc/X11, open the file [Link] in an editor and search
for "nvidia". After the line BoardName "Quadro M6000" (or whatever card you are
using) insert a new line that reads BusID "PCI:7:0:0" according to the entries found
in the log files before. Save and close the [Link] file and type startx. If X still
refuses to start, try the other entries found in the Xorg log files.
• You need the installation script to uninstall the driver. Thus, if you want to be able to
uninstall the NVIDIA software you need to keep the installer script.
• Be aware of the fact that you need to reinstall the NVIDIA drivers if your kernel is
updated as the installer needs to compile a new kernel module in this case.
16
To uninstall NVIDIA drivers, select "NVIDIA Drivers" from the "App & features" list and
press the "Uninstall" button (see fig. 2). After the uninstall process has finished you will
be prompted to reboot.
[Link]/SIMULIA c Dassault Systèmes GPU Computing Guide 2025
Start the installer with the "–uninstall" option. This requires root permissions.
18
• All GPUs with HBM2 memory (like P100, V100, A100, H100) are equipped with ded-
icated ECC resources, so turning ECC off doesn’t change the performance, at least
not significantly. So ECC can and should be turned on.
[Link]/SIMULIA c Dassault Systèmes GPU Computing Guide 2025
• All GPUs with GDDR6 and similar memory types should turn ECC off for best perfor-
mance since ECC reduces the available resources of the GPU. In more detail: The
available memory is reduced by 6.25% (storage needed for ECC bits). In addition the
memory bandwidth is reduce up to 20% due to fetching ECC bits for each memory
transaction.
Usually ECC can be turned off safely since broken GPU memory often leads to crashes or
unstable results. If that’s the case it is recommended to enable ECC temporarily as a diag-
nostic tool to determine whether the problems are caused by a GPU memory defect. Please
also refer to section 13.
The ECC feature can be managed by using either the NVIDIA Control Panel or the com-
mand line tool nvidia-smi. Please note that the following commands have to be run as
administrator.
This procedure works on all supported versions of Windows and on all supported Linux dis-
tributions.
The command requires administrator privileges on Windows and root privileges on Linux,
respectively.
5. To disable ECC: Please execute the following command for each of the GPUs:
nvidia-smi -i <number_of_the_GPU_card> -e 0
19
6. To enable ECC: Please execute the following command for each of the GPUs:
nvidia-smi -i <number_of_the_GPU_card> -e 1
7. Reboot.
[Link]/SIMULIA c Dassault Systèmes GPU Computing Guide 2025
20
3. Search for the term "ECC State" in the navigation tree of the dialog and open the "ECC
State" page of the dialog by clicking on the tree item.
4. Disable or enable the ECC feature for all Tesla devices (see fig. 3).
[Link]/SIMULIA c Dassault Systèmes GPU Computing Guide 2025
Figure 3: Switch off the ECC feature for all Tesla cards.
21
When available, the GPUs have to operate in TCC mode4 . Please enable the mode, if not
[Link]/SIMULIA c Dassault Systèmes GPU Computing Guide 2025
yet enabled.
Please note that the following commands require administrator privileges.
6. Reboot.
If available, this feature should always be enabled. However, under certain circumstances
you may need to disable this mode.
Please note that the following commands require administrator privileges.
6. Reboot.
• "Exclusive Process" means only one context is allowed per device, usable from multiple
threads at a time.
In case of "Exclusive Process" the user has to make sure that no other process is running
on the GPU before he starts a GPU solver run using CST Studio Suite.
• The TCC Mode of the card cannot be used. This deteriorates the performance.
Because of these limitations we recommend using an additional graphics adapter for the
graphics output, or if available, an onboard graphics chipset.
23
the Local System account (see fig. 4). The CST Studio Suite installer installs the service by
default using the correct account.
Download and install the latest CST Service Pack prior to running a simulation or HWAccDi-
agnostics.
only.
Example: Open a shell (cmd on Windows, or bash on Linux) and enter
• set CUDA_VISIBLE_DEVICES=0
on Windows or
• export CUDA_VISIBLE_DEVICES=0
on Linux to bind all CST solver processes started from this shell to the GPU with ID 0. To
make the setting persistent for all CST instances started on the system you may add the
variable to the global system environment variables.
The CST Distributed Computing (DC) system can be used to assign the GPU cards of a
multi-GPU system to different DC Solver Servers. The solver processes executed by a cer-
tain DC Solver Server will only be able to access the GPU cards assigned to this Solver
Server (see fig. 5). Please refer to the online help documents of CST Studio Suite (sec-
tion "Simulation Acceleration", subsection "Distributed Computing") to learn more about the
setup and configuration of the DC system.
5
Execute the command nvidia-smi -L to get the GPU IDs of your cards.
26
[Link]/SIMULIA c Dassault Systèmes GPU Computing Guide 2025
nvidia-smi -q -d CLOCK
27
Before making any changes to the clocks, the GPU should be set to Persistence Mode.
Persistence mode ensures that the driver stays loaded and does not revert back to the default
clock once the application is complete and no CUDA or X applications are running on the
GPU.
To enable persistence mode use the following command:
[Link]/SIMULIA c Dassault Systèmes GPU Computing Guide 2025
nvidia-smi -pm 1
nvidia-smi -q -d SUPPORTED_CLOCKS
Please note that the supported graphics clock rates are tied to a specific memory clock rate
so when setting application clocks you must set both the memory clock and the graphics
clock6 . Do this using the -ac <MEM clock, Graphics clock> command line option.
Execute the following command to reset the application clocks back to default settings.
nvidia-smi -rac
Please be aware that the application clock setting is a recommendation. If the GPU can-
not safely run at the selected clocks, for example due to thermal or power reasons, it will
automatically lower the clocks to a safe clock frequency. You can check whether this has
occurred by typing the following command while the GPU is active:
nvidia-smi -a -d PERFORMANCE
[Link]/SIMULIA c Dassault Systèmes GPU Computing Guide 2025
29
• If you experience problems during the installation of the NVIDIA driver on the Win-
dows operating system please try to boot Windows in "safe mode" and retry the driver
installation.
• NVIDIA DGX A100 and NVIDIA HGX A100 8-GPU server-systems: "cudaGetDevice-
Count returned errorcode 802: system not yet initialized"
Please make sure nVidia fabric manager is installed and activated.
[Link]/SIMULIA c Dassault Systèmes GPU Computing Guide 2025
• Please note that CST Studio Suite cannot run on GPU devices when they are in "ex-
clusive mode". Please refer to section 10.3 on how to disable this mode.
• If you are using an external GPU device ensure that the PCI connector cable is se-
curely fastened to the host interface card.
• Uninstall video drivers for your existing graphics adapter prior to installing the new
graphics adapter.
• Make sure the latest motherboard BIOS is installed on your machine. Please contact
your hardware vendor support for more information about the correct BIOS version for
your machine.
• Use the HWAccDiagnostics tool to find out whether your GPU hardware and your driver
is correctly recognized.
• GPU temperatures are crucial for the performance and overheating of GPU devices
can lead to hardware failures. Please refer to section 11.8 for details.
30
• A faulty GPU device can be responsible for seemingly random solver crashes. To
ensure that your GPU is working properly please run tests provided by the HWAccDi-
agnostics tool found in the CST installation. Examples of usage:
–deviedID=0 will run the same simulation as before on device ID 0 only (helps to
verify problems usually related to a specific GPU).
– Please run HWAccDiagnostics_AMD64 –h to see all possible options.
• In case simulations are getting unstable when running on the GPU it’s recommended
to check the GPU memory by switching on the ECC feature on the GPU (see 10.1).
• If a GPU is not recognized during the installation please check if Memory Mapped I/O
above 4GB is enabled in your bios settings.
• TCC mode: GPUs running in WDDM instead of TCC mode might eventually fail during
memory allocations. It is highly recommended to put all GPUs in TCC mode to avoid
these kind of problems (see 10.2).
If you need further assistance please contact your local 3DS/SIMULIA support team
([Link]
31
• Please note that currently only the Time Domain Solver (FIT) supports AMD GPUs.
• Please note that a 64 bit computer architecture is required for GPU Computing.
• CST Studio Suite officially supports the AMD GPUs listed in the table below. That
[Link]/SIMULIA c Dassault Systèmes GPU Computing Guide 2025
means that these GPUs are tested and validated with CST software and you can con-
tact CST support in case you run into any problems.
• Please do not combine different GPUs in a single host system for GPU Computing.
• Platform = Servers: These GPUs are only available with a passive cooling system
which only provides sufficient cooling if it’s used in combination with additional fans.
These fans are usually available for server chassis only!
• Platform = Workstations: These GPUs provide active cooling, so they are suitable for
workstation computer chassis as well.
• GPUs with reduced FP64 performance (e.g. GPUs where the FP64 performance is
less than half the speed of the FP32 performance) are not well suited for solvers which
require a high FP64 performance. Pease check chapter 2 Supported Hardware for
affected solvers.
• Memory and problem size: For the Time Domain Solver (FIT) the rule of thumb is
"available memory divided by 100" (e.g. a GPU with 16 GB of Memory will be sufficient
for a simulation with 160 million meshcells. The memory consumption is dependent on
the used features, so the maximum simulation size might be more or less than that).
32
The AMD GPUs that fulfill the following requirements may be enabled for simulations:
The recommended drivers will work for all supported AMD GPUs.
17 History of Changes
The following changes have been applied to the document in the past.
Date Description
Aug 8 2024 add DDM solver for GPU support, add H100 NVL GPU
Nov 19 2024 add A800 PCIe 40Gb Active to list of supported GPUs
The environment variable CUDA_VISIBLE_DEVICES can be set to limit the use of specific GPUs in systems with multiple GPUs. This allows a user to specify a subset of GPUs that CST Studio Suite should utilize for simulations. By doing this, it enhances control over computational resource allocation, potentially optimizing performance for specific workloads or configurations by targeting the most suitable GPUs in the array .
The Distributed Computing (DC) system in CST Studio Suite is useful in multi-GPU environments where it assigns specific GPUs to different DC Solver Servers, preventing resource contention and ensuring equitable distribution of computing tasks. This enhances simulation efficiency by optimizing the use of available GPU resources, thus reducing bottlenecks and ensuring better load distribution across servers during computations .
Using the Display Link feature on Tesla GPUs prevents the use of TCC mode as it requires display functionalities. This subsequently reduces GPU computational performance because resources have to be divided between display tasks and computing applications, leading to decreased performance in high-demand computational tasks. For optimum performance, it is recommended to use a separate graphics adapter or onboard graphics for display output, preserving TCC mode for computational tasks .
AMD GPUs are supported for CST Studio Suite only if they are listed as tested and validated, supporting the Time Domain Solver (FIT). GPUs not in the supported list but meeting certain criteria such as at least 4 GB memory can be enabled, though use of untested hardware is not recommended. Limitations include potential lack of support from CST for issues arising from unsupported hardware usage, and the requirement not to mix different GPUs in one system, which can cause compatibility issues .
GPU Boost is a feature that dynamically increases the core and memory clock rates based on available power and thermal headroom, enhancing performance. For CST solvers on Tesla GPUs, this translates to potential improvements in performance because the GPU Boost feature utilizes unused power capacity for higher computational throughput, adjusting clock speeds based on workload demands. Users can manage this feature via NVIDIA System Management Interface or control panel to achieve desirable performance .
The Particle-In-Cell (PIC) solver has specific constraints when used with GPU support in CST Studio Suite. Modulation of external fields, open boundaries, and certain emission models are not supported, alongside other limitations such as multi-GPU support. Recommendations include ensuring fixed boundary conditions and proper verification of GPU compatibility before deployment, considering these constraints impact solver execution and accuracy .
TCC (Tesla Compute Cluster) mode is significant because it assigns the GPU resources specifically to applications, enhancing performance by eliminating overhead created by sharing resources with the display, as required in WDDM (Windows Display Driver Mode). This mode is necessary for optimal performance in A-solver GPU computing, as it allows exclusive access to GPU resources, thus preventing contention that decreases computing efficiency .
Using TCC mode, NVIDIA GPUs can dedicate more resources to CST applications by eliminating contention with display processes, crucial for multiprocessing and shared computing scenarios. This improves the efficiency of task execution in CST Studio Suite. In shared computing environments, the use of Exclusive Compute Mode ensures that resources aren't monopolized by non-critical processes, thus enhancing parallel processing efficiency by limiting GPU use to one active context per device when necessary .
ECC (Error Correction Code) should be enabled for GPUs with HBM2 memory, such as P100, V100, A100, and H100, as turning it off does not significantly alter performance. For GPUs with GDDR6 or similar memory, ECC should usually be turned off for optimal performance since enabling it reduces available resources by 6.25% and decreases memory bandwidth by up to 20%. ECC can be enabled temporarily for diagnostic purposes to determine memory defects, as it often leads to unstable simulations when memory errors occur .
For AMD GPUs used with CST Studio Suite, it is recommended to use verified driver versions: 23.x for both Windows and Linux. These versions are preferred because they have been tested to ensure compatibility and optimal performance with CST software, reducing potential issues during operation. Using other driver versions might also work, but they could introduce unverified changes impacting stability and performance. Following the proper installation guidelines from AMD ensures proper driver setup .