Some Tests with bigger fea models...
ANSYS Mechanical 19.2 - linear static with frictional contacts - 12 load steps incl. Restarts - 13.1 mio DOF - PCG-Solver - DMP 10 cores
Memory used 37 GB
Elapsed time [sec] - Ryzen 9 3900 vs. Gold 6136:
25617 vs. 21124
--
ANSYS Mechanical 17.2/19.2/2020 R1 - linear static with frictional contacts – 8 load steps incl. Restarts - 11.4 mio DOF - Sparse-Solver out-of-core - DMP 10 cores
in-core uses 143 - 175 GB RAM
out-of-core uses 55 - 78 GB RAM
Elapsed time [sec] out-of-core - Ryzen 9 3900 vs. Gold 6136:
14334 vs. 11265 (ANSYS 17.2)
xxxxx vs. 10731 (ANSYS 19.2 - On Ryzen ANSYS stopped due to lack of RAM for sparse out-of-core)
13243 vs. 8978 (ANSYS 2020 R1)
This fea model causes lots of I/O (1,8 TB written to disk) due to out-of-core computing.
ANSYS 2020 R1 on the Gold 6136 is very impressive.
It uses just 56 GB RAM for out-of-core and just 143 GB for in-core.
The previous versions of ANSYS were using 72-78 GB RAM and 175 GB.
ANSYS 2020 R1 was approx. 10-15% faster than 19.2
In-core is approx. 15 % faster.
The Benefit of AVX-512 makes ANSYS 19.2 approx. 10-15 % faster than ANSYS 17.2.
--
Ryzen R9 3900 works at approx. 3.8 - 4.0 GHz (Cooling on Max.) running ANSYS on 10 cores.
AMD Ryzen 9 3900 12-core (TDP 65 W) - SSE4.2, AVX, AVX2 - 3.1 to 4.3 GHz
L1-Cache 768 KB
L2-Cache 6 MB
L3-Cache 64 MB
2 x 32 GB DDR4 RAM 2660 MHz
PCIe SSD max. 1 GB/sec
--
Gold 6136 works at approx. 3.4 - 3.5 GHz running ANSYS on 10 cores.
Intel Xeon Gold 6136 12-core (TDP 150 W) - SSE4.2, AVX, AVX2, AVX-512F - 3.0 to 3.7 GHz
L1-Cache 768 KB
L2-Cache 12 MB
L3-Cache 24.8 MB
6 x 32 GB DDR4 ECC RAM 2660 MHz
PCIe SSD max. 3 GB/sec (for reading I could see 2 GB/sec here while running ANSYS)
--
The Ryzen 9 3900 with it's low TDP and just two memory lanes performes quite well.
The Threadripper or Ryzen PRO might be better here, because of more memory lanes and higher clock speeds (higher TDP).
But the main librays of the program have to support AVX2. This can be done for ANSYS in Batch mode with the MKL-Tweak "set MKL_DEBUG_CPU_TYPE=5".
Defining a system variable MKL_DEBUG_CPU_TYPE with value 5 doesn't work for my Windows 10 installation.
Eine Antwort auf diesen Beitrag verfassen (mit Zitat/Zitat des Beitrags) IP