3 ms·
There‘s applications that use these chips like it were real-time systems (because it‘s the only thing financially possible for them). For these use cases, 20% w
by Joeri 9y ago
There‘s applications that use these chips like it were real-time systems (because it‘s the only thing financially possible for them). For these use cases, 20% will hurt, a lot.
Applications that use these chips in a realtime capacity don’t share hardware with other apps, so it will be possible to deploy them on unpatched machines, even if inconvenient. Those workloads are also not big on context switching and so not affected much by the patch.
I think cloud hosting providers will hurt the most, because that tends to be a context-switch-heavy workload, and their pricing model assumes a certain level of performance per core. They’ll mix in AMD in significant quantities just to diversify and avoid getting burned in the same way. They’re probably also the biggest market for intel’s server line.
This incident will seriously hurt intel even if they handle it perfectly, which they’re not doing.
- m_mueller 9y agoYes, that's a good point. The sharing of hardware over the internet (aka the 'cloud') is the most critical market here. Though, I think there's a lot of cross pollination between cloud and HPC markets - if AMD is financially successful with Zen they'll be able to pour more R&D money into fortifying their position. The question is of course whether that's going to be enough - Intel came back and beat out all competition after their last big loss of market share (~2005, 95nm process spawning AMD64 / Opteron). I'd argue that the Intel of 2018 is not the Intel of 2005. From what I'm hearing/reading, they've had an ongoing brain drain from being too much focused on short term profits versus taking real risks in developing new technologies as well as putting up the finances to actually secure and test their cash cows.