4 ms·
The i7-2600k doesn't even have 256-bit busses on the inside. The i7-2600k barely begun to implement AVX (and doesn't even implement AVX2). The i9-9900k is way
by dragontamer 8y ago
The i7-2600k doesn't even have 256-bit busses on the inside. The i7-2600k barely begun to implement AVX (and doesn't even implement AVX2).
The i9-9900k is way better. 3x 256-bit execution ports, 64-byte (512-bit) messages going around the Ringbus, DDR4 RAM (double memory bandwidth).
The raw clocks ignore the huge advancements in IPC that exist between Sandy Bridge and Coffee Lake. And even then, the 5GHz clock on the i9-9900k makes it completely incomparable to compare the ancient Sandy Bridge with the modern Coffee Lake.
- blihp 8y agoIf you roll up all of the 'huge advancements' (IPC, clock speed, all of it) over the course of 7 years, that's probably in the neighborhood of what we used to call the 'annual upgrade.' Ancient? Yes. Incomparable? No.
- dragontamer 8y agoThe Pentium 4 Netburst architecture was relatively stagnant between the years 2000 and 2004. "Prescott" (2004) was still "Netburst" but Prescott includes AMD64 so I'd say that's a major change. Still, its reflective in the naming. Netburst, Willamette, Northwood, Prescott, and Tejas were all called "Pentium 4", and lasted from a time period from year 2000 to 2006. Sure, there were a few additions: Hyperthreading I guess. But otherwise, the main difference in this timeframe were the 250nm to 90nm scaling (which got "free" GHz upgrades back then without any effort) In short: > what we used to call the 'annual upgrade.' You're exaggerating. Progress has slowed but Willamette (year 2000 1.5GHz) vs Northwood (year 2002 2GHz) Pentium 4s weren't that dissimilar. Prescott (2004) is even more amusing, as it hit 3.8GHz (Intel Pentium 4 570J). But boy, oh boy... you really can't compare Prescott 3.8GHz against Sandy Bridge (2011, 3.6GHz) or Coffee Lake (2018, 3.6GHz ), even if the base clocks are all close.
- blihp 8y agoAnd luckily we had AMD then, as we do now (only recently), to pick up the slack. Sure I'm exaggerating a bit, but no more than you are to say 'incomparable'. Intel upgrades for the last 7 years have been modest at best. If you need a new machine, sure they'll make a fine replacement. But hardly a reason to upgrade year over year (or even every 2-3 years) for performance and/or functionality alone. I've been sitting on an old i7 Sandy Bridge precisely because Intel hasn't been offering me a compelling reason to upgrade. I'm probably going to finally do it next year... but it won't be to another Intel system.
- tracker1 8y agoMy 5yo i7-4790K is to this day very fast (gtx 1080, and nvme 2 years ago). May upgrade next year for more threads/vms though.
- ksec 8y ago1. Sandy Bridge to Skylake combined makes barely a double digit gain in IPC, ~roughly 14%. I hardly called that a "huge advancements" in IPC over 7 years time. 2. We have already proved should the SandyBridge Overclocked to 4GHz+ it would have perform faster in some cases than Skylake Uarch with same Clock Speed. Remember SandyBridge was 32nm. 3. "Netburst, Willamette, Northwood, Prescott, and Tejas " You made it sounds as if there were many generation. All of them are part of Netburst uArch and Willamette was the first Gen, Tejas was cancelled. So there is only "Willamette, Northwood, Prescott". Each with much improved Clock speed, better implementation of HT, better memory controller and cache read improvement, and finally AMD64, all translate to substantial performance improvement, regardless of its power usage. Netburst may not be a good uArch, but it definitely brings many improvement, the writing was on the wall in 2004 and we got Core 2 in 2006. And we have been stuck with Quad Core Desktop CPU despite we have had over 4x transistor density improvement.
- coldtea 8y ago>The i9-9900k is way better. 3x 256-bit execution ports, 64-byte (512-bit) messages going around the Ringbus, DDR4 RAM (double memory bandwidth). All those don't matter if they hardly make a 10-15% difference in everyday use, and require specialized code to take advantage of.
- celrod 8y agoMuch of what I do is vectorized, so the more fma units and the side wider, the faster. So avx512 > avx2 with two 256 bit units > avx2 with two 128 bit units. But my work (statistics) seems poorly represented in benchmarks and the community at large. Ryzen is in the later group, and gets rave reviews. While most press I've seen talking about avx512 has been negative. Yet I get a lot more flops out of the 10-core i9 7900x than the similarly priced 16-core Threadripper 1950x in simulations. A big part of that is probably doing most of my work in Julia, where because the code you run is compiled locally the first time a function/argument type combination is called (a) code will be generated for all your CPU's features, and (b) it is easy to encourage aggressive optimizations to vectorized code by the compiler, eg by parameterizing arrays by their bounds. R benchmarks will not see benefits at all, as much of R's math libraries are terribly unoptimized -- the default BLAS doesn't even use any runtime dispatch! (Thankfully it's easy to change, but the benchmarks all reflect that reality -- and most people's personal experiences too). Similar likely applies to many NumPy benchmarks, but depending on the distributor of those binaries, the situation likely isn't better. Either generic unoptimized binaries, or shipping with something like Intel MKL which, while the fastest linear algebra library for Intel processors, dispatches to slow code paths for AMD processors -- a very unfair choice for benchmarking. I'm less less familiar with NumPy though, so perhaps there's a booth fair and well optimized distribution. I fear the future will move against my use cases.
- marmaduke 8y agoIf you want fat vector units you should be on a GPU.
- dragontamer 8y ago
- mrb 8y ago«The i9-9900k is way better...» You forgot the most important: i9-9900k has TWICE the number of cores as i7-2600k.