- Joined
- Jun 22, 2006
- Messages
- 1,050 (0.16/day)
| System Name | Beaver's Build |
|---|---|
| Processor | AMD Ryzen 9 5950X |
| Motherboard | Asus ROG Crosshair VIII Hero (WI-FI) - X570 |
| Cooling | Corsair H115i RGB PLATINUM 97 CFM Liquid |
| Memory | G.Skill Trident Z Neo 32 GB (2 x 16 GB) DDR4-3600 Memory - 16-19-19-39 |
| Video Card(s) | NVIDIA GeForce RTX 4090 Founders Edition |
| Storage | Inland 1TB NVMe M.2 (Phison E12) / Samsung 950 Pro M.2 NVMe 512G / WD Black 6TB - 256M cache |
| Display(s) | Alienware AW3225QF 32" 4K 240 Hz OLED |
| Case | Fractal Design Design Define R6 USB-C |
| Audio Device(s) | Focusrite 2i4 USB Audio Interface |
| Power Supply | SuperFlower LEADEX TITANIUM 1600W |
| Mouse | Razer DeathAdder V2 |
| Keyboard | Razer Cynosa V2 (Membrane) |
| Software | Microsoft Windows 10 Pro x64 |
| Benchmark Scores | 3dmark = https://www.3dmark.com/spy/32087054 Cinebench R15 = 4038 Cinebench R20 = 9210 |
If looking at the geometric mean across dozens of benchmarks carried out, the new CPU microcode update lowered the performance by 1~2%. With the new CPU microcode, the cost of the default mitigations on Cascade Lake with this dual Xeon Platinum server was just ~1%. Having TSX enabled and thus TSX Async Abort in place meant losing a few percent on performance while TAA combined with Hyper Threading is where the performance was about 15% lower compared to the best results. So at least out-of-the-box there is just a small (but still noticeable, particularly from the new CPU microcode -- though again in the future ideally to be addressed via toolchain updates to offset most of those hits) performance hit from these mitigations except when disabling Hyper Threading or having TSX support enabled where TAA then introduces a new and real performance penalty.
https://www.phoronix.com/scan.php?page=article&item=cascadelake-jcc-taa&num=1
https://www.phoronix.com/scan.php?page=article&item=cascadelake-jcc-taa&num=1