There's no simple solution for Spectre, as is it much more widespread and affects pretty much every modern CPU. The only viable way is some sort of software-based mitigation.
De Raadt's rant was about Meltdown though, and he's absolutely right. Meltdown is a Intel-only fuckup; someone decided that protection domains should not apply to execution speculation in order to boost performance.
The impact of FDIV was a floating point precision error after the fourth digit on 1 in 9 billion divides. Meltdown is a bug allowing unauthorized code to read all protected memory available on all Intel CPUs manufactured over the last ~2 decades.
Datacenters which already patched are apparently getting a performance hit in the high two-digits. Epic, for example, has people complaining because users cannot connect to game servers after the patch doubled servers CPU load.
No, it is not. There were a number of F00F bug workarounds, all implementable at OS level and with negligible (if any) performance hit.
Meltdown is nothing like it. The performance impact depends largely on the load type the CPU experiences, but it is estimated to range between 5% and 30% - which is terrible.
Both AMD and Intel routinely put out addendums detailing bugs on their CPUs and chipsets. These are normally addressed at BIOS or OS level.
This is different though. Meltdown and Spectre are a result of how branch prediction works on pretty much all modern CPUs and are difficult - if not impossible - to shield from on existing hardware.
It's even worse; Bannon was officially part of the National Security Council.
Which means he had a security clearance. Which means he very likely lied to the FBI during vetoing about the Don Jr. / Russia meeting he now acknowledges.
Well, it mustn't be that far off if its mere announcement managed to detonate all ties between Trump and Bannon and have the WH sending cease-and-desist letters over the span of a single day.
And the thing is not even out yet. We'll see in a week.
I just wish they'd go ahead and say "live it's saturday night" and end the skit. The joke has gone on long enough. It's old.
Seriously. The thing today where Trump videoconferenced into a WH press briefing when he literally sits 100 feet away from the room was surreal. I was expecting Alec Baldwin to show up at any moment.
Yes, several, and i'm guessing you already know this. The requirements for services managing that users and those many QPSs are completely different from "traditional" websites such as Craigslist, where a small number of users will be active at a time hitting mostly common cached data. Once you scale at 20x you reach a point where throwing hardware at the problem doesn't help anymore and the entire architecture must be rethinked - load management, monitoring, content (even static) serving, storage sharding and propagation... hell, even how you develop and release changes dramatically.
Now, i'm not saying that Twitter needs 3000+ employees. But what they do and how they do it is not simple either.
He's going to die horribly because he thinks science lies to all to us.
There's little to cheer here.
even if those 5 Republicans had voted for the bill, it would not have passed (hint 50+5 60)
And yet, they didn't.
The voting failed 50-49, with 5 Republicans voting no and 5 Democrats voting yes. Trying to pin this down on Democrats alone is, at best, naive.
There's no simple solution for Spectre, as is it much more widespread and affects pretty much every modern CPU. The only viable way is some sort of software-based mitigation.
De Raadt's rant was about Meltdown though, and he's absolutely right. Meltdown is a Intel-only fuckup; someone decided that protection domains should not apply to execution speculation in order to boost performance.
Well, it is likely. Still, that graph is horrible to look at.
The impact of FDIV was a floating point precision error after the fourth digit on 1 in 9 billion divides. Meltdown is a bug allowing unauthorized code to read all protected memory available on all Intel CPUs manufactured over the last ~2 decades.
Gauge their seriousness as you wish.
Datacenters which already patched are apparently getting a performance hit in the high two-digits. Epic, for example, has people complaining because users cannot connect to game servers after the patch doubled servers CPU load.
No, it is not. There were a number of F00F bug workarounds, all implementable at OS level and with negligible (if any) performance hit.
Meltdown is nothing like it. The performance impact depends largely on the load type the CPU experiences, but it is estimated to range between 5% and 30% - which is terrible.
You know, he's not wrong. This is, in impact, way bigger than Intel's FDIV fiasco and that ended up in recalls.
I love my Asus UX305CA.
...just because you plaster something in a license doesn't make it automatically law.
https://blog.twitter.com/offic...
Both AMD and Intel routinely put out addendums detailing bugs on their CPUs and chipsets. These are normally addressed at BIOS or OS level.
This is different though. Meltdown and Spectre are a result of how branch prediction works on pretty much all modern CPUs and are difficult - if not impossible - to shield from on existing hardware.
It's even worse; Bannon was officially part of the National Security Council.
Which means he had a security clearance.
Which means he very likely lied to the FBI during vetoing about the Don Jr. / Russia meeting he now acknowledges.
No. I'm surprised he decided to release an official POTUS statement and cease-and-desist letter over this very particular piece of "fake" news though.
Makes you wonder.
I sort of agree. The POTUS released an official statement about Bannon shortly after the book was announced, for Pete's sake.
Guess there's more truth to it than the WH cares to admit: https://twitter.com/janicemin/...
Didn't Trump himself suggest he recorded his conversations with Comey, like, 75 years ago?
Both were triggered by the announcement of Wolff's book.
Judging by the amount of "fake news" Trump denounces every chance he gets it is kinda suspicious this book triggered him enough to file lawsuits...
A better question is why Twitter hasn't shut down Trump's account over TOC violations yet.
(yeah, the obvious answer is that Twitter is hemorrhaging money and will cling at anything to say relevant in the eyes of their VCs).
Well, it mustn't be that far off if its mere announcement managed to detonate all ties between Trump and Bannon and have the WH sending cease-and-desist letters over the span of a single day.
And the thing is not even out yet. We'll see in a week.
I just wish they'd go ahead and say "live it's saturday night" and end the skit. The joke has gone on long enough. It's old.
Seriously. The thing today where Trump videoconferenced into a WH press briefing when he literally sits 100 feet away from the room was surreal. I was expecting Alec Baldwin to show up at any moment.
Sheeze, couldn't with start 2018 without 17 breaking news from the WH a day?
Yes, several, and i'm guessing you already know this. The requirements for services managing that users and those many QPSs are completely different from "traditional" websites such as Craigslist, where a small number of users will be active at a time hitting mostly common cached data. Once you scale at 20x you reach a point where throwing hardware at the problem doesn't help anymore and the entire architecture must be rethinked - load management, monitoring, content (even static) serving, storage sharding and propagation... hell, even how you develop and release changes dramatically.
Now, i'm not saying that Twitter needs 3000+ employees. But what they do and how they do it is not simple either.
Craigslist serves ~60 million users. Twitter is around a billion. No, they're not equal in complexity.