4 ms·
I can’t find in the article what is so special about skylake that enterprises would delay their purchases.
by cm2187 9y ago
I can’t find in the article what is so special about skylake that enterprises would delay their purchases.
- tomalpha 9y agoIMHO it’s less about Skylake being special and more about the previous generations having fairly small improvements over their predecessors. Broadwell was never a huge leap for general purpose server performance. At least it didn’t get perceived as such. It seemed to concentrate on being good at the low power end to compete with ARM and more virtualization features iirc. For some, rather like phones these days: they’re good enough not to need a refresh as often as they might have been. For others Skylake is the first real jump / change in performance (the cache hierarchy and core interconnect topology changes are particularly interesting to me). For yet others, they delayed refreshing for longer than they used to: “we might as well wait until the next release now”. And once Skylake was out in all its thousand-different-sku glory they bought it. Edit: typo
- rincebrain 9y agoBroadwell for servers was noteworthy for the Xeon-D line, which has some neat performance characteristics in a tiny power envelope, but it was very targeted at the laptop market - hell, there were only 6 models of desktop processors, compared to 32 laptop models, or 50+ server processors (half of which are the Xeon-D line, and the other half were so delayed that the E3 Skylakes landed before the E5 Broadwells did, and then the E5 Skylake equivalents got delayed forever, presumably in part to finally also support the socketable Xeon Phis Intel wanted so much)
- mtgx 9y agoCannon Lake was also supposed to arrive right after Skylake. I think it's been delayed to 2019 now.
- jandrewrogers 9y agoAs someone who waited for the new server CPUs, the microarchitecture made a few changes that should substantially improve its performance for data-intensive workloads: - 6 memory channels (instead of 4) - new CPU cache architecture that should show big gains for things like databases - new vector ISA (AVX-512) that is significantly more useful than AVX2, in addition to being twice as wide The first two should be instant wins for things like databases. AVX-512 isn't going to be used in much software yet but it is arguably the first broadly usable vector ISA that Intel has produced. This should enable some significant performance gains in the future as code is rewritten to take advantage of it. (Not idle speculation on the latter, we're queued up to get some of this hardware for exactly this purpose. Previously vectorizing wasn't worth the effort outside of narrow, special cases but AVX-512 appears to change that.)
- zbjornson 9y agoHave you found benchmarks yet for the second point (DB perf)? I assume by "new cache architecture" you're referring to the switch from a ring to a mesh for L3, which was almost necessitated by having more cores in SKL. But at the same time they reduced associativity from 8 to 4 (worse) and made L1-L3 non-inclusive (unsure of the effects yet). They did expand L2 a bit though.
- jandrewrogers 9y agoNo benchmarks yet (and it will be difficult to isolate that effect). The cache structure more closely mirrors the data locality intrinsic in recent high-performance database engines, which don't share data pages across cores and which now commonly use page sizes (256k) that don't fit in L2. The increase in cache size from 256k to 1M is particularly important because it allows you to store multiple pages in L2 which should make a number of multi-page and complex query on single page operations significantly more efficient. Should be great for join kernels. Similarly, the non-inclusive and smaller shared L3 makes more sense in that the amount of state shared across cores is actually pretty small. In short, it redistributes cache resources in a way that is very useful to the way database engines are currently designed.