GPU for DEM and SPH simulation: sizing memory, FP64 and SM licences for Ansys Rocky
Eurokommerz, Vienna, since 2006: Private AI/ML · IT Managed Services · Enterprise Training · AI Hardware & Software
- Ansys's Rocky GPU buying guide (April 2026) sets priorities by case: higher double-precision performance for shaped particles, memory bandwidth for spheres, single-precision performance and bandwidth for SPH
- In Rocky's 2026 R1 benchmarks 32 million spheres in a rotating drum used 47 to 50 GB of GPU memory, 16 million polyhedra 43 to 46 GB and 32 million polyhedra up to 90 GB
- Rocky licenses GPUs by streaming multiprocessors: the base licence covers up to 112 SMs per job and each HPC task adds 14, so one RTX PRO 6000 with its 188 SMs already needs one HPC-8 licence by our arithmetic
- NVIDIA rates the H200 NVL at 30 TFLOPS of FP64 and 4.8 TB/s; the RTX PRO 6000 Server Edition offers 120 TFLOPS of FP32 and 1,597 GB/s but computes FP64 at 1/64 of its FP32 rate
- The guide advises keeping all GPUs in one server; distributed GPU runs across nodes are a beta since 2026 R1, for spheres without coupling on Linux only
Supplied by Eurokommerz: NVIDIA RTX PRO 6000 Blackwell Check price and availability →
Which GPU for Ansys Rocky
For Ansys Rocky the particle shape decides the card. Simulations with shaped particles, polyhedra for example, need strong FP64, which among the cards we supply means the NVIDIA H200 NVL; sphere-only cases depend on memory bandwidth and SPH on single-precision speed and bandwidth, where the NVIDIA RTX PRO 6000 Blackwell in its Workstation or Server Edition fits. After that, GPU memory sets how many particles fit, and Rocky's licence counts the card's streaming multiprocessors.
DEM, the discrete element method, follows every particle of a bulk material and its contacts, which is how mixers, chutes, mills and conveyors are simulated. SPH, smoothed particle hydrodynamics, represents a fluid itself as particles, used for splashing, wading or free-surface flows. Rocky does both on GPUs, and the figures here come from Ansys's "Rocky GPU buying guide" on Ansys Innovation Space, marked "Last Updated: April/2026", which we read on 25 October 2026.
The guide is explicit about priorities. For shaped particles it advises prioritising "higher double-precision performance"; for spheres only, higher memory bandwidth and, for very large cases, more memory; for SPH, high single-precision performance, memory bandwidth and enough memory for millions of elements. It adds that cards with weak double precision but good bandwidth do well on spheres and poorly on shaped particles. Where SPH and DEM run together, the bottleneck can be either one, depending on particle counts and shapes.
Rocky DEM GPU requirements: memory per million particles
Rocky's 2026 R1 benchmarks report total GPU memory for typical cases, run on H100, A100 and L40 cards. We divided each figure by the particle count to get a planning value per million, and from that the particles that fit on 96 GB and 141 GB.
| ROCKY CASE | MEMORY | GB PER MILLION | ON 96 GB | ON 141 GB |
|---|---|---|---|---|
| Drum, 32 M spheres | 47 to 50 GB | about 1.5 | about 60 M | about 90 M |
| Drum, 16 M polyhedra | 43 to 46 GB | about 2.8 | about 33 M | about 49 M |
| Drum, 32 M polyhedra | up to 90 GB | about 2.8 | about 34 M | about 50 M |
| Cyclone, 185 M spheres | 77 GB, one GPU, CFD-DEM | about 0.42 | about 230 M | about 330 M |
| SPH, Rocky's estimate | 35 M in 80 GB | about 2.3 | about 42 M | about 61 M |
Ansys Innovation Space, "Rocky GPU buying guide", last updated April 2026, 2026 R1 benchmarks (rotating drum, cyclone separator with one-way Fluent coupling, car wading), read 25 October 2026. Per-million values and particle counts are our arithmetic from nominal card memory, rounded down, without headroom.
Two things follow. The memory per particle depends on the case, not only the particle type: the spheres of the cyclone take less than a third of the memory per million of the spheres in the drum. Rocky itself writes that the 90 GB of its 32 million polyhedra could hold about 185 million spheres, close to the cyclone and far from the drum. Size from a case of your own, run on any GPU, and scale the measured memory to the target count. The second point is coupling: in the cyclone, multi-GPU runs used about 92 GB against about 77 GB on one GPU, 17 per cent more, so a coupled case split over cards needs that margin. For SPH, the car wading case with 16 million elements peaked at about 27 GB across two GPUs.
The minimum requirements in the guide are at least 4 GB of GPU memory, fast double precision, CUDA compute capability 6.0 or higher and a driver that supports CUDA 12.8 or higher. RTX PRO Blackwell cards have compute capability 12.0. The guide's recommended lists name the A30, A100, L40, H100, H100 NVL and H200 among server cards and Ampere-generation RTX cards among workstation cards, and calls the A100 "the Rocky team's preferred choice". No Blackwell RTX PRO card is named. They meet the memory, compute capability and driver minimums; whether their FP64 rate counts as "fast" in the guide's sense is for Ansys to confirm, which is why we place them on sphere and SPH cases, not on shaped particles.
FP64, FP32 and bandwidth of the cards we supply
| CARD | FP64 | FP32 | BANDWIDTH | MEMORY |
|---|---|---|---|---|
| H200 NVL | 30 TFLOPS | 60 TFLOPS | 4.8 TB/s | 141 GB HBM3e |
| RTX PRO 6000 Server Edition | about 1.9 TFLOPS | 120 TFLOPS | 1,597 GB/s | 96 GB GDDR7 |
| RTX PRO 6000 Workstation | about 2.0 TFLOPS | 125 TFLOPS | 1,792 GB/s | 96 GB GDDR7 |
| RTX PRO 5000 72 GB | not published | 65 TFLOPS | 1,344 GB/s | 72 GB GDDR7 |
NVIDIA H200 product page and RTX PRO product pages and datasheets; RTX PRO 6000 FP64 is our arithmetic from the 1/64 rate in NVIDIA's RTX Blackwell PRO architecture whitepaper, since the product pages list none.
Read against Rocky's priorities, the table gives a clear split. For shaped particles the H200 NVL has about 16 times the FP64 rate of an RTX PRO 6000, by our arithmetic, and three times the bandwidth. For sphere-only cases the H200 NVL's 4.8 TB/s is the higher bandwidth, while the RTX PRO 6000 holds the same order of particles per card and, in its Workstation Edition, also drives the screens for setup and post-processing. For SPH the RTX PRO 6000 has twice the FP32 rate and the H200 NVL three times the bandwidth; we found no published Rocky result that sets the two cards against each other, so a test run of one of your SPH cases on both is the way to decide. Our FP64 GPU server comparison explains the 1/64 rate, and our comparison of GPU memory bandwidth covers the other cards.
We supply both card families, as cards or in workstations and servers built for Rocky; send us your particle counts, shapes and whether you couple with Fluent, and our team replies with a configuration.
Rocky multi-GPU licences, counted by streaming multiprocessors
Rocky does not license per card. The guide states that licensing "is based on the total number of SM's across all GPU's irrespective of the number of GPU's", that all SMs of a card are used, that the base licence covers one job with up to 112 SMs, and that one Rocky HPC task enables 14 more; an HPC-8 licence holds 8 tasks, 112 SMs. NVIDIA's whitepaper lists 188 SMs for the RTX PRO 6000 Blackwell Workstation and Max-Q Editions. The Server Edition has the same 24,064 CUDA cores, which at 128 cores per SM gives 188 by our division.
| GPUS IN ONE JOB | SMS | HPC TASKS | HPC-8 LICENCES |
|---|---|---|---|
| 1 × RTX PRO 5000 | about 110 | 0 | none |
| 2 × RTX PRO 5000 | about 220 | 8 | 1 |
| 1 × RTX PRO 6000 | 188 | 6 | 1 |
| 2 × RTX PRO 6000 | 376 | 19 | 3 |
| 4 × RTX PRO 6000 | 752 | 46 | 6 |
Licence rules from the Rocky GPU buying guide (April 2026); SM counts from NVIDIA's RTX Blackwell PRO whitepaper (RTX PRO 6000) and, for the RTX PRO 5000, our division of NVIDIA's 14,080 CUDA cores by 128 per SM; tasks and licences are our arithmetic, rounded up. Confirm the count with your Ansys channel.
The RTX PRO 5000, in its 48 or 72 GB version, is by this arithmetic just inside the base licence, which makes it a sensible single-card Rocky workstation when the cases fit its memory. The SM count of the H200 NVL is not listed on NVIDIA's H200 product page or in the H200 NVL product brief we opened, so ask your Ansys channel for its licence count before you compare a server of H200 NVL cards with RTX PRO 6000 cards. The licence count, the card's FP64 rate and its memory together decide which card suits a case, which is why we size from your cases.
One server or several
Rocky runs several GPUs in one machine within the licence rules above. Across machines the guide is cautious: since 2026 R1 distributed GPU computing is a beta that applies only to spheres without coupling, on Linux, and the guide advises keeping all GPU cards in a single server because distributed runs are not fully supported. A team that expects to grow should therefore plan the chassis for the final card count from the start. Our article on how many GPUs fit in one server explains the slot, power and airflow limits.
On speed, Rocky's benchmarks compare GPUs with a 48-core Intel Xeon Gold 6542Y: up to 41 times faster for DEM with several GPUs, about 18 times for CFD-DEM on one GPU and 31 times on several, and for SPH about 23 times on one GPU in the worst case and about 65 times on two. Those runs used H100, A100 and L40 cards, not the cards in our tables.
| CONFIGURATION | FOR | AT THE WALL |
|---|---|---|
| Workstation, RTX PRO 5000 | one 72 GB card: spheres, SPH, within the base licence | follows the workstation |
| Workstation, RTX PRO 6000 | one or two cards: spheres, SPH, setup and post-processing | follows the workstation |
| Server, 2 × H200 NVL | shaped particles, CFD-DEM | about 2.0 kW |
| Server, 4 × H200 NVL | large polyhedra cases, several jobs | about 3.4 kW |
| Server, 4 × RTX PRO 6000 SE | SPH and sphere cases for a team | about 3.4 kW |
Our reading of the Rocky GPU buying guide. Wall power is our estimate (cards at 600 W, two AMD EPYC 9355, plus 15 per cent), as in our four-card and H200 NVL server guides, and is confirmed by a measurement on the delivered system.
For CFD-DEM, Rocky couples with Ansys Fluent, whose GPU solver follows its own memory and SM licence rules; our CFD simulation guide sets them out. For shaped-particle work, our guides to the two-card and four-card H200 NVL server cover chassis and power, and for SPH the four-card RTX PRO 6000 Server Edition server. Process engineering departments that also plan AI work will find the wider picture in our article on AI servers for manufacturing companies. If you are unsure which card your mix of cases needs, describe the cases and the licence you hold and we size the card count to it.
What we supply
You can buy this system from us: our team sizes the configuration to your workload and budget and replies within one business day. We supply the RTX PRO 6000 in its Workstation, Max-Q and Server Editions, the RTX PRO 5000 and the H200 NVL as cards, and build workstations and servers to order, assembled and tested before delivery, on one EU contract and invoice, with manufacturer warranty on every component and the assembly covered by us. Operating system and driver are installed on request. Quantities and lead time are confirmed in writing with the quote.
FAQ
What is the best GPU for Ansys Rocky?
How much GPU memory does Rocky need?
How is Rocky licensed on several GPUs?
Does Rocky need double precision?
Can Rocky run across several GPU servers?
Where can I buy a GPU workstation or server for Rocky in Europe, and what does it cost?
We supply RTX PRO 6000 and RTX PRO 5000 workstations and H200 NVL servers for Rocky DEM and SPH, sized to your particle counts and licence. Describe your task in a few sentences and our team will help. We reply within one business day.
Talk to an expertWe reply within one business day