- Joined
- Feb 18, 2005
- Messages
- 5,950 (0.82/day)
- Location
- Ikenai borderline!
System Name | Firelance. |
---|---|
Processor | Threadripper 3960X |
Motherboard | ROG Strix TRX40-E Gaming |
Cooling | IceGem 360 + 6x Arctic Cooling P12 |
Memory | 8x 16GB Patriot Viper DDR4-3200 CL16 |
Video Card(s) | MSI GeForce RTX 4060 Ti Ventus 2X OC |
Storage | 2TB WD SN850X (boot), 4TB Crucial P3 (data) |
Display(s) | Dell S3221QS(A) (32" 38x21 60Hz) + 2x AOC Q32E2N (32" 25x14 75Hz) |
Case | Enthoo Pro II Server Edition (Closed Panel) + 6 fans |
Power Supply | Fractal Design Ion+ 2 Platinum 760W |
Mouse | Logitech G604 |
Keyboard | Razer Pro Type Ultra |
Software | Windows 10 Professional x64 |
Because you the user can easily shut down your PC, pull out the current memory modules, replace them with different ones, turn the PC back on and expect everything to Just Work.Ok, i undestand the whole thing.
But why it has to be done every times ?
I'm asking because the silicon on the RAM doesn't change every time.
It's like an OC of a processor, when you got the good timings and the stability you want, it's ok for good, you don't have to re-do the OC stuff again every lauch.
"But I haven't changed my memory modules" you say. Well the UEFI has no way of knowing that because there's no way (AFAIK) to reliably "fingerprint" a specific memory module, so it can't trust that the 16GB module that was in RAM slot 1 yesterday is the same 16GB module in RAM slot 1 today. If it did, and the memory module was actually different, and it simply applied the same timings as it had previously used, the system would probably fall over.
And that's the number one thing that users don't want: instability. So the UEFI spends more time in the boot process to ensure that the system is less unstable.
Why is this only a problem for DDR5? Because DDR4 has been around so long that all its quirks and weirdnesses are well-known and understood and coded into the UEFI, so there's no need for your system to to spend lots of time learning DDR4 module characteristics. But DDR5 is new and AM5 is new and AMD hasn't figured out DDR5 on AM5 completely yet, so they're being cautious with boot times to ensure that people don't complain that AM5 is an unstable platform. As the platform matures the boot times will come down (we've already seen this) until eventually they'll be at DDR4 levels again.