5 ms·
Far from an expert, but applying general high level engineering principles I would guess it's related with the accelerating complexity needed to get linear perf
by davnicwil 7y ago
Far from an expert, but applying general high level engineering principles I would guess it's related with the accelerating complexity needed to get linear performance gains, especially as the lower hanging hardware fruit has been picked.
I know a bit about the meltdown/spectre bugs and that seemingly was the case there: essentially a software hack to get more performance out of literally the same hardware. That was done to increase performance, but of course there were unintended consequences that nobody foresaw or cared to look for. It's almost obvious looking with hindsight - no free lunch etc.
- kingosticks 7y agoIf there is an increase you could probably attribute some of it to the increasing costs of re-spinning. The same bug that will have been fixed in previous generations may not be deemed bad enough today.
- hyperman1 7y agoI look at spectre as a proof that low hanging fruit of software bugs is finally getting picked. Theoretical knowledge of these kinds of bugs goes back for decades, but nobody bothered to look for them in practice. Why would you, when most programs contain enough invalid pointers to hack them at will. But the state of the art has advanced, so now people start looking at other stuff. Integer overflow are another example of a class of bugs ignored for a long time.