- Joined
- Aug 20, 2007
- Messages
- 22,212 (3.44/day)
- Location
- Olympia, WA
System Name | Pioneer |
---|---|
Processor | Ryzen 9 9950X |
Motherboard | MSI MAG X670E Tomahawk Wifi |
Cooling | Noctua NH-D15 + A whole lotta Sunon, Phanteks and Corsair Maglev blower fans... |
Memory | 128GB (4x 32GB) G.Skill Flare X5 @ DDR5-4200(Running 1:1:1 w/FCLK) |
Video Card(s) | XFX RX 7900 XTX Speedster Merc 310 |
Storage | Intel 5800X Optane 800GB boot, +2x Crucial P5 Plus 2TB PCIe 4.0 NVMe SSDs, 1x 2TB Seagate Exos 3.5" |
Display(s) | 55" LG 55" B9 OLED 4K Display |
Case | Thermaltake Core X31 |
Audio Device(s) | TOSLINK->Schiit Modi MB->Asgard 2 DAC Amp->AKG Pro K712 Headphones or HDMI->B9 OLED |
Power Supply | FSP Hydro Ti Pro 850W |
Mouse | Logitech G305 Lightspeed Wireless |
Keyboard | WASD Code v3 with Cherry Green keyswitches + PBT DS keycaps |
Software | Gentoo Linux x64, other office machines run Windows 11 Enterprise |
I was afraid not from memory access penalty which as you say is the same, but from penalty associated with inter-die communication such as: process migration from one die to another, inter-process communication between several processes across the separate dies (which in my case would be avs2yuv.exe sending it's finished frames from one die, while the encoder process x264 is running on another)
There isn't really a means to mitigate this except to disable two cores. It just is how things work.