• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

Intel bug incoming? Meltdown and Spectre exploits

Intel is already facing a fight in the server space from not only AMD but other companies. They probably need this like a hole in the head right now.

Desktop users won't give a monkeys though if the performance hit is negligible right now, what will be interesting though is if AMD is not affected and their new CPU close the gap on Intel and AMD keep their more cores for less money stance too, Intel will have a bigger fight on their hand.

Right now in the desktop space Intel has an IPC and clockspeed lead, if they both reduce and AMD catches up within reasonable distance, Intel will have problems.
 
Hmm, it says the fix will significantly slow down CPU performance. I guess we need to avoid that patch on gaming PCs. It will be something really specific that only effects certain tasks that 95% of people won't be doing. Yet the update will be pushed on everyone.

But let me guess. The next generation will have the fix and be just as fast? ;)

The security risk is a danger to everyone, its the performance hit that the patch causes that might not effect the majority of tasks too much.
 
Insightfull. Source?

So it apparently effects every call into the kernel (so every syscall), and the reports are that every syscall will take a 50% performance hit. Now some applications will get an absolute hammering (virtualization like you say and anything that does a LOT of IO). But that no way what so ever should be equated to 'it won't really effect' home users.
 
Intel is already facing a fight in the server space from not only AMD but other companies. They probably need this like a hole in the head right now.

Desktop users won't give a monkeys though if the performance hit is negligible right now, what will be interesting though is if AMD is not affected and their new CPU close the gap on Intel and AMD keep their more cores for less money stance too, Intel will have a bigger fight on their hand.

Right now in the desktop space Intel has an IPC and clockspeed lead, if they both reduce and AMD catches up within reasonable distance, Intel will have problems.

But only if AMD keeps undercutting them on price. They are only doing that now because they don't have the lead.
 
So it apparently effects every call into the kernel (so every syscall), and the reports are that every syscall will take a 50% performance hit. Now some applications will get an absolute hammering (virtualization like you say and anything that does a LOT of IO). But that no way what so ever should be equated to 'it won't really effect' home users.

This site suggests games and desktop apps won't really be affected.


translate.googleusercontent.com/translate_c?depth=1&nv=1&rurl=translate.google.com&sl=auto&sp=nmt4&tl=en&u=https://www.hardwareluxx.de/index.php/news/hardware/prozessoren/45319-intel-kaempft-mit-schwerer-sicherheitsluecke-im-prozessor-design.html&usg=ALkJrhg--IiIqA7LOGozMMSS3ccCy0y9cQ
 
But we've had the vulnerability for 10 years, so why bother now :p

Plus it sounds more like something that would be used in a targeted attack on host machines, not random desktop users.
 
But we've had the vulnerability for 10 years, so why bother now :p

Plus it sounds more like something that would be used in a targeted attack on host machines, not random desktop users.

Because no one knew about it, now the cat is out of the bag, it needs to be patched before exploits are developed.
 
But we've had the vulnerability for 10 years, so why bother now :p

Plus it sounds more like something that would be used in a targeted attack on host machines, not random desktop users.

If it ain't broken... no wait if it is broken... I'm confused :p
 
Well the frames per second speaks for itself, there's a small hit, but it is small.
So with this bug it's going to be very different depending what application (be that a game or not) is doing (is it reading from disk, is it using network IO etc). I would not take any benchmark seriously at this point apart from the synthetic ones demonstrating the raw problem...
 
Back
Top Bottom