391–400 of 499 posts
Earlier quoted context omitted.
13xx, 15xx, 17xx, ThreadRipper. For gen 2, that'd be: 23xx, 25xx, 27xx, ThreadRipper. I think they picked the names/numbers to show some kind of equivalence with i3/5/7, but that's not quite it.
ThreadRipper seems more like a Xeon competitor to me. Something for the server room crowd.
Threadripper is their workstation CPU.
Earlier quoted context omitted.
Does Google innovate? -ss
Have you seen how many messaging apps theyve made in the last few years?
Earlier quoted context omitted.
Yes. Their arch is just different, they where not affected by meltdown and the chances of a spektre exploit actually working are very small. I don't know why that is the case but basically amd is 99% free from this story.
They aren't. Spectre works fine on AMD. They avoided Meltdown only because their cores are less optimised. Meltdown isn't Intel specific - Apple cores were also affected. It's clear that AMD weren't doing anything special w.r.t. side channel attacks. They were just further behind in the optimisation race and as a consequence, were less hit.
Let the benchmarks roll in... https://access.redhat.com/security/vulnerabilities/L1TF-perf An estimation of man hours spent on this issue outside Intel https://www.servethehome.com/intel-publishes-l1tf-and-foresh... Thought frequently mentioned, Phoronix did not run a benchmark comparing before and after application of the microcode update. Excerpt: To note, no microcode changes/updates were made to the systems under…
Is this net-positive for VMware since customers will be required to buy more licenses for the same workload?
Or is it net-negative because it makes public clouds more competitive?
Before Zen, we all kind of assumed they were so far ahead that AMD were more likely to be out of business before they would ever be a credible threat again. I actually thought Intel must have had some tricks up their sleeves in terms of performance gains that we hadn't seen yet, simply because there was no market need to roll them out and they had so many years of coasting on marginal gains. Seeing them taking this s…
>Before Zen, we all kind of assumed they were so far ahead that AMD were more likely to be out of business before they would ever be a credible threat again. It depends where about on the timeline. AMD's hired of Lisa Su and Jim Keller in 2012, we all thought it was too little too late. Look back at the Roadmap Intel were giving at the time, I used to joke about Tick Tock were like the sound of AMD's death clock. In…
Earlier quoted context omitted.
wasn't bell labs part of a very big corporation when they invented basically everything about the modern world?
Bell Labs invented Google, Facebook, etc? Wow, did not know that. But as you say, the labs were a very small, independent part of a very big corporation, which is likely why they did interesting things. The other thing is that they were forced by the government to license transistor patents to others, who actually created almost everything else. By your theory the military invented the internet, so they invented the…
Earlier quoted context omitted.
But CPU+FPGA will forever be a tiny niche, right? I don't see any path where mainstream programs get a boost from FPGA.
Not at all. Specialized coprocessors are mainstream actually - from network cards offloading to small chip in every iPhone, and for a reason. The obvious way forward is universal specialized coprocessors, reprogrammable for the task(s). Better if tightly integrated with the memory, buses and CPUs. The weak side of FPGA historically is programmability and especially the tools. But since the interest for FPGA is growin…
There are uses for FPGAs where there's enough money at stake for the hardware development but the number of units is small - stuff like high frequency trading or many defense roles. Or in the development of new hardware. But it's pretty niche.
Earlier quoted context omitted.
"Doesn't this show that it is time for someone to set up some kind of ..." I don't think this is necessary ... I think "circumventing" this benchmarking restriction is as simple as having one person purchase an Intel CPU and just drop it on the ground somewhere ... and have another person pick it up off of the street (no purchase, no EULA, no agreement entered into) and decide to benchmark the found item against othe…
I think that one has to apply the microcode patches after startup. For this, you have to obtain the microcode patch file from somewhere. So I am not sure whether this "legal hack" will work.