News for hackers. Stuff that matters.
Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by Waterluvian on Saturday January 06, 2018 @11:35AM (#16085941)
Isn't that like saying that it turns out this car we sold can only do 150, not 200. But it's okay because most of you never drive above 80 anyways.

You're right. Most people who just surf the Netflix and download the YouTubes will not notice. But it's still a form of fraud, even to those who never max out CPU. I think fraud is a strong word knowing that this wasn't intentional. But they sold a lesser product than they advertised and need to make customers whole. Otherwise it pretty much is fraud.

Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by anonacct37 on Saturday January 06, 2018 @12:07PM (#16086140)
I think people are underestimating how bad webapps are. I do... a lot of computing and by far the most CPU intensive applications on my computer are webviews. Either Gmail in chrome or slack. I'm actually going to be upgrading my laptop soon because slack+3 organizations crushes my laptop.

Do you think browser vendors have been pushing JIT research forward, investing in webasm, and building things like servo because websites are so fast and light on CPU?

[deleted]
Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by mistercow on Saturday January 06, 2018 @12:33PM (#16086353)
Is that remotely feasible? You're basically suggesting that Intel needs to refund or replace every PC and server CPU they've sold in the last five years.

The fdiv recall cost Intel almost half a billion dollars, and that was for a small subset of processors that most people didn't replace. Intel has a lot of assets, but replacing five years worth of CPUs might actually bankrupt them.

Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by forgotpw2018 on Saturday January 06, 2018 @12:43PM (#16086424)
I deleted that because I thought it was too flamey after reading it again, but yeah refunding everyone is unrealistic.

Maybe just average out the performance impact across large cloud providers and offer that as a percentage? It probably wouldn't be hard for a company like Google to crunch metrics before/after the update and give a number for how much their performance has been affected

Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by mistercow on Saturday January 06, 2018 @01:41PM (#16086744)
Yeah, I think it's clear that some amount of risk has to be absorbed by the public. It sucks, but it's in our best interest to keep pushing computing forward. And we should keep in mind that it's also not like these attacks are obvious. They took security researchers four years to find.

I think the important thing here is precedent, rather than making customers whole. The question then is what, if anything, could Intel have done to anticipate and prevent this, and how do we incentivize them to take those measures in the future?

It's also possible that there's nothing to change here. There's always going to be some risk, and trying to force that risk closer and closer to zero will at some point not be worth the tradeoff. As bad as this is, if the caution necessary to prevent it would have resulted in processors being half as fast as they are today anyway, there wouldn't be any point.