Originally posted by pipe13
View Post
For us mere mortals, this feature is probably not for any real day-to-day use. For the Amazon and Googles who've got millions of cores I'm sure every millisecond counts when you're testing some feature and it takes 10 minutes for your giant server farm to reboot and do it's thing. For that use case, yeah, I can see how shaving off MANY seconds might help in getting you home in time for a dinner that's still hot. Someone out there will get annoyed enough to make a valiant attempt at figuring it out but how many massive datacenters are still running anything major off 1st gen Zen stuff? Probably not too many. Thus why AMD sees not much value in trying to dig into the cause. And even if they determine it's a BIOS / UEFI / CPU firmware cause, I doubt any MoBo maker's gonna issue a BIOS or CPU firmware update for it.
If they can work around it through CPU detection a la "if CPU=Zen || Zen+ {enableParallelBringUp=false}" then yay for AMD I guess...so long as it doesn't shit the bed using that kind of kludge. The devs seem to be agreeing that it's an all or none use case for AMD. Probably a safe bet.
Comment