Hacker News new | past | comments | ask | show | jobs | submit
close04 | on: A live tree of systemd jobs on the boot console
On many machines with DDR5 you get the lengthy memory training every boot and that comes on top of the already long UEFI initialization time.
bmicraft | parent | next
Surely that could run in parallel with initializing everything else, with the amount of CPU cache modern CPUs have?

Also the soldered ram couldn't have changed from last boot, so reuse the last training? That's exactly what I mean.

loading story #50465770
crote | root | parent
The training reuse is already happening on machines with regular user-replaceable DIMM modules. It's why there is such a scary long wait on the first boot of a newly-assembled system, but not subsequent ones.

So even if it can change, starting out with a simple "Are the same modules still installed?" check saves a lot of time.

dathinab | parent
> training every boot

except this should only happen _once_ (until you remove/replace components, reset the BIOS etc.). Which is why it normally doesn't happen for laptops, it was run once in the factory and DDR being soldered one mean they can just "fixed" disable the retraining avoiding bugs in the "retraining needed" detection

but yes, there are pretty bad motherboards out there, like the one I have turned out to be a complete shit show with multiple sever design issues I unluckily "lucked out of not running into" in the first 2 years of usage making a return unlikely and a replacement is useless as this is are fundamental issue affecting all models AFIK.