There’s an incredible lengthy reply in this thread, which is completely made up.
The thing is that to run those 1 & 0, it has to, technically, store them in a physical way so that it can be passed through to what’s next. As it’s 0 & 1, it’s not encrypted or protected. It’s pure raw data. The encryption and protection are usually done after the data has passed through the processor… by a task handled by the processor (ironically). Now, what they have “found” (which is false. it’s has been known since the 80’s) is that it’s possible to access this raw data by force feeding some 0 & 1 to the processor which can be hidden in anything and makes it start an hidden small software which, for example, could send a copy of the raw data through the web.
I saw hints of the truth in there which I thought were pretty funny. Like the bit about force feeding 1s and 0s I assumed was referring to specially crafted instructions to starve the CPU cache or trick the branch predictor or something. Hilarious.
Unfortunately AMD historically hasn’t had the management and the stockholder return to take on Fortress Intel. So Intel board hires weasel CEO’s to exploit the situation. Ironically, the tech is more than good enough.
It already is. Across the board 30% hit is fairly common on cloud services. So the hit is worse than say, Apple and it’s battery/clock down issue, but clearly Intel weasels think they can outlast it - what are you going to do, not buy more Intel?
I looked at the graph, and it’s actually above 2x CPU utilisation increase, unlike what the reddit title said; however, this is virtual machines we’re talking about; who is to say that the extra increase is not attributed to moving to a different host, CPU type or some other type of VM-based consolidation?!
There’s an incredible lengthy reply in this thread, which is completely made up.
Fascinating.
It’s not just completely made up, it’s gibberish.
This almost sounds like it was written by some AI…
Looks more like a markov chain to me.
I saw hints of the truth in there which I thought were pretty funny. Like the bit about force feeding 1s and 0s I assumed was referring to specially crafted instructions to starve the CPU cache or trick the branch predictor or something. Hilarious.
Permalink for those who want it: https://www.epicgames.com/fortnite/forums/news/announcements/132642-epic-services-stability-update?p=132713#post132713
This is going to get expensive for companies pretty quickly.
So that means buying more servers, with… Intel processors in them!
Maybe. With the slowdown that KPTI incurs, it makes EPYC even more attractive.
Now whether AMD can fab enough to keep up with demand is another question.
Unfortunately AMD historically hasn’t had the management and the stockholder return to take on Fortress Intel. So Intel board hires weasel CEO’s to exploit the situation. Ironically, the tech is more than good enough.
It already is. Across the board 30% hit is fairly common on cloud services. So the hit is worse than say, Apple and it’s battery/clock down issue, but clearly Intel weasels think they can outlast it - what are you going to do, not buy more Intel?
I looked at the graph, and it’s actually above 2x CPU utilisation increase, unlike what the reddit title said; however, this is virtual machines we’re talking about; who is to say that the extra increase is not attributed to moving to a different host, CPU type or some other type of VM-based consolidation?!
Time to start using userspace network drivers like https://github.com/snabbco/snabb in order to reduce the number of context switches.