Originally posted by dekernel
View Post
Announcement
Collapse
No announcement yet.
Google Has A Problem With Linux Server Reboots Too Slow Due To Too Many NVMe Drives
Collapse
X
-
- Likes 2
-
Originally posted by F.Ultra View Post
AFAIK it can't be anything else than a write back cache that causes the NVMe driver to wait so the question you should ask yourself is what crazy sized write back caches that Google uses that takes 4.5 seconds to flush on a NVMe...
- Likes 4
Leave a comment:
-
Leave a comment:
-
I just realized that with this patch if I buy a second NVMe my PC will shutdown 4.5 seconds faster. So it's not just about cloud servers.
- Likes 1
Leave a comment:
-
Originally posted by milkylainen View PostUmm. But WHY is it taking 4.5 seconds?
There is nothing that should take 4.5 seconds on an NVMe drive.
Even if it has a power hold-up cache, it would be flushed rather immediately.
Buggy drive or bugged specification?
- Likes 1
Leave a comment:
-
Google almost certainly have more NVMe drives per server than they're letting on. 16 is probably just enough to cross the 60 second threshold. They're a hyperscalar, they pack things as densely as possible.
At the same time, this may well be a holdover from their previous generation of servers. It's just only now finally working is way from their prod-kernel into the mainline.
Leave a comment:
-
Originally posted by DRanged View PostAh remember the old days IBM p43 servers booting just within 7 minutes. Those fond memories.
- Likes 1
Leave a comment:
-
Originally posted by caligula View PostWow, so many comments and nobody is wondering why few seconds matter. After all you'll reboot a desktop only once per day, servers have uptime of months. So shouldn't matter even if it takes few hours to boot.
- Likes 2
Leave a comment:
-
Originally posted by dekernel View Post
Guess I would be interested in knowing just what OS you are using that requires daily updates because even Windows 2003 could go a full week before required reboots from the Windows Updates.
- Likes 2
Leave a comment:
Leave a comment: