Not of you need to wait for ever for an update to finish during shutdown, when you just want to pack up your laptop and finally leave the work site - and afterwards it somehow needs the same time to boot up again, because it’s preparing out finishing something, without ever telling you, what the hell it’s actually doing all the time
And usual reboot only takes like 20s, you’re right there, but not with a windows update blocking a normal shutdown or startup
If it’s just a service or two, then it’s pretty quick.
Obviously you need to know, what you’re doing.
And I think that’s pretty hard with windows, because it never tells you, what it’s actually doing during an update.
With Linux it’s much more transparent and often the restart of a service is just part of my update routine.
No need to close and save all my open stuff, and reboot. Just restart the few services that got an update and that’s pretty much it.
So, really depends on the update, the transparency of it and also the personal insight/skill
Computers actually got slower to boot after DDR5. It was true that ultrafast boot would boot in something like 5 seconds from post, now auto memory timings are harder to get right and so require more iterations to achieve stability.
Doesn’t memory training only happen once when you first boot the machine (or reset bios).
I mean having a lot of ram will take a long time to post, but that’s not unique to DDR5. My server is DDR4 with 64 gigs of ram and with it’s original CPU it took ages for the post to finish.
There are memory trainings that happen automatically every time the machine is booted. The more intense ones happen after a full shut down, but ddr4 was far less noticeable than the intense ddr5 trainings which often even need an additional power cycle to get right. These are not your typical automatic timings applied in the bios, they’re trial and error timings set by the firmware of the motherboard I believe.
Sure, if you’re not multitasking and running uninterruptible or PITA-to-get-going-again processes or are just in a good flow where it’ll take way more than 20 seconds to reopen all the programs you had running and breaks it
I had to update a Chromebook-like machine that was running Windows not to long ago. It was excruciating. The restart progress bar on one update after reboot took ~30 minutes to reach 3%.
Keep in mind that the computer is unusable during this time, and all it takes is one poweroff to brick the machine. Ask me how I know :) . I had to leave it plugged in overnight to finish.
If this comment is referring to Windows reboots after update, I will call it confidently incorrect.
A modern computer will restart and be up and running again within like 20 seconds. This just gives off i aM vErY sMaRt vibes.
Not if it’s running Windows
Yes, even windows.
Not of you need to wait for ever for an update to finish during shutdown, when you just want to pack up your laptop and finally leave the work site - and afterwards it somehow needs the same time to boot up again, because it’s preparing out finishing something, without ever telling you, what the hell it’s actually doing all the time
And usual reboot only takes like 20s, you’re right there, but not with a windows update blocking a normal shutdown or startup
There is no situation where fucking about like they describe is the better option over rebooting
Well, depends on what you need to restart.
If it’s just a service or two, then it’s pretty quick.
Obviously you need to know, what you’re doing.
And I think that’s pretty hard with windows, because it never tells you, what it’s actually doing during an update.
With Linux it’s much more transparent and often the restart of a service is just part of my update routine.
No need to close and save all my open stuff, and reboot. Just restart the few services that got an update and that’s pretty much it.
So, really depends on the update, the transparency of it and also the personal insight/skill
Computers actually got slower to boot after DDR5. It was true that ultrafast boot would boot in something like 5 seconds from post, now auto memory timings are harder to get right and so require more iterations to achieve stability.
Doesn’t memory training only happen once when you first boot the machine (or reset bios).
I mean having a lot of ram will take a long time to post, but that’s not unique to DDR5. My server is DDR4 with 64 gigs of ram and with it’s original CPU it took ages for the post to finish.
There are memory trainings that happen automatically every time the machine is booted. The more intense ones happen after a full shut down, but ddr4 was far less noticeable than the intense ddr5 trainings which often even need an additional power cycle to get right. These are not your typical automatic timings applied in the bios, they’re trial and error timings set by the firmware of the motherboard I believe.
Sure, if you’re not multitasking and running uninterruptible or PITA-to-get-going-again processes or are just in a good flow where it’ll take way more than 20 seconds to reopen all the programs you had running and breaks it
Na, nothing enterprise boots that fast. Not even with nvme drives.
I had to update a Chromebook-like machine that was running Windows not to long ago. It was excruciating. The restart progress bar on one update after reboot took ~30 minutes to reach 3%.
Keep in mind that the computer is unusable during this time, and all it takes is one poweroff to brick the machine. Ask me how I know :) . I had to leave it plugged in overnight to finish.
If this comment is referring to Windows reboots after update, I will call it confidently incorrect.