SC111 — 24-Core CFD HPC Node with 12-Channel Memory and 128 MB Cache for ANSYS Fluent

The SC111 node is the strongest all-round parallel tier in the lineup. It runs a single AMD EPYC 9255 — 24 cores and 48 threads at a 4.0 GHz all-core boost — on AMD's full server platform, with 128 MB of L3 cache and twelve DDR5 memory channels behind it. That combination matters: a high core count is only as useful as the bandwidth and cache feeding it, and SC111 has more of both than any other node at this core count. Paired with 128 GB of RAM and 2 × 1.88 TB NVMe SSD, it's the node to choose when your case scales well and you want nothing in its way.

Specifications

Three specs work together here. Twenty-four cores give Fluent a wide parallel spread. Twelve memory channels — roughly 600 GB/s per socket — keep every one of those cores supplied with data instead of queuing for it. And 128 MB of L3 gives each partition room to keep its working set on-chip. The 4.0 GHz figure is the all-core boost, the clock the node holds with every rank loaded, not a single-core peak that collapses under a full job.

What this node is built for

SC111 is the top parallel tier: core count, bandwidth, and cache all at once. It suits:

• Cases that scale well across many cores — 24 MPI ranks split a mesh far finer than a 16-core node, and with real bandwidth behind them, that translates into shorter wall-clock time rather than stalled cores.

• Bandwidth-heavy physics — multiphase, combustion, many transported scalars, coupled solvers: cases that move a lot of data per iteration and would choke a narrower memory bus.

• Large parameter sweeps and design studies — more cores means more work per hour, so you get through more design iterations per day.

• Long sustained runs — an all-core clock held under full load matters more across a multi-day transient than a peak that only ever appears on one core.

• Transient, LES, and DES runs writing heavy data — NVMe storage keeps large data files and frequent autosaves from slowing down the solve.

Choosing SC111

SC111 doesn't trade one factor away to lead on another — it has more cores than our 16-core tiers, more bandwidth than any desktop-platform node, and the largest cache in the lineup at this core count. Choose it when:

• Your case scales efficiently past 16 cores, with enough cells per partition to keep each rank busy relative to the boundary data it exchanges, and

• Your solve is limited by throughput, bandwidth, or working-set size rather than by single-thread speed.

If your case doesn't scale past a handful of cores, or is gated by serial sections and UDF execution, a high-clock 8-core tier will finish it sooner despite having a third the cores — clock speed beats core count when a case can't use the cores. And if memory capacity is your constraint rather than throughput, our high-memory nodes are the right tool. As a rough guide, Fluent needs about 1 GB of RAM per million cells for a typical steady, single-phase case, so with 128 GB, SC111 handles meshes well beyond what a 32 GB node can hold.

Tell us your cell count, physics, and how your case scales with core count, and we'll point you to the right tier.

Fast NVMe storage

The two 1.88 TB NVMe SSDs give substantially higher read/write throughput than SATA SSDs, plus nearly 3.76 TB of combined capacity — which matters more on a high-throughput node, where a fast solve shouldn't be held up waiting on disk. That means faster loading of large case and data files, quicker autosaves, and room to keep a full DOE sweep's output on disk without constantly clearing space.

How parallel solving works on this node

When you run Fluent in parallel, the solver partitions your mesh across all 24 cores (using algorithms such as METIS), each core solving its share of cells and exchanging boundary data each iteration via MPI. On a single node, that communication runs through fast on-board channels rather than a network, keeping parallel overhead low. Between exchanges, each core pulls cell data from memory — and this is where a 24-core node either delivers or doesn't. With twelve memory channels and 128 MB of shared L3, SC111's cores aren't queuing for a narrow path to RAM as the partition count rises, so the core count actually converts into throughput.

Why rent instead of buy

For engineers whose cases scale well and whose bottleneck is throughput rather than single-thread speed, SC111 delivers the cores, the bandwidth, and the cache together — and you can still drop to a high-clock tier when a case calls for it instead.

How it works — you're in full control

SC111 is yours to drive directly. You connect to the node over a secure remote desktop connection and run everything yourself, exactly as you would on a local workstation:

1. Connect via remote desktop — you get full remote access to the SC111 node.

2. Set up your simulation — load your geometry and case, configure your solver settings, and run ANSYS Fluent with all 24 cores at your command.

3. Run and monitor in real time — start, pause, adjust, and watch the solution as it progresses, with complete control throughout.

4. Keep your results — post-process on the node or download your solution and data files whenever you're ready.

You have full authority over the node for the duration of your rental: we provide the hardware and the support, and you run the simulations your way.

Frequently asked questions

How is SC111 different from our other 24-core node? Same core count and a similar all-core clock, but SC111 has twelve memory channels instead of eight and 128 MB of L3 cache. On bandwidth-bound cases, that wider memory path is the difference; on cases limited by other factors, the two perform closely.

How does it compare to our 16-core server nodes? Half again as many cores at the same bandwidth class. If your case scales efficiently past 16 ranks, SC111 finishes it sooner; if it doesn't, the extra cores mostly sit idle and a 16-core tier is the better value.

Will 24 cores always be faster than 8 or 16? No. Fluent scales well only as long as each core has enough cells to stay busy relative to the data it exchanges with its neighbors. On a small case, splitting it 24 ways can leave cores spending more time communicating than computing — and a faster 8-core node would finish first. We'll help you size it right.

Is 4.0 GHz slow compared to a 5.7 GHz node? On a single thread, yes. But 5.7 GHz figures are single-core peaks that come down under a full parallel load. SC111's 4.0 GHz is the all-core number, held with all 24 cores working — which is what a real parallel solve sees.

How large a mesh can it handle? With 128 GB of RAM, plan for meshes well into the tens to low hundreds of millions of cells for simpler steady single-phase cases, fewer for transient or multiphase physics (about 1 GB of RAM per million cells is a good starting estimate). Send us your case for a precise answer.

What if my case needs more memory than cores? For large, memory-bound simulations we offer higher-memory nodes — we'll recommend the right tier so you get the capacity, or the throughput, your case actually needs.

Is my data kept confidential? Yes.

Get started with SC111

If your cases scale well across many cores and you want core count, memory bandwidth, and cache working together rather than trading off, SC111 is built for exactly that.

Contact MR CFD to run your ANSYS Fluent case on SC111 — and we'll help you choose between throughput and clock speed for your simulation.