http://videocardz.com/51380/intel-haswell-e-i7-5960x-i7-5930k-i7-5820k-pricing-revealed
6 Cores 12 HT @ 389.
hmm not bad
6 Cores 12 HT @ 389.
hmm not bad
I think the most interesting CPU in the lineup is the 5930K. The 8 cores of the 5960X are great but 3Ghz is a bit pathetic given there are quad cores with the same architecture running at 4Ghz and I'm pretty sure there are Ivy based Xeons with 8 cores running at more than 3Ghz.
At 3.5Ghz though the 6 core 5930 looks pretty nice.
For those interested in the raw specs it can use over 68GB/s of memory bandwidth (the entire DDR3 bandwidth available to the XBO) and has a SIMD capacity 672 GFLOPS.
You can always count on Intel to be cutting-edge on both tech and evil.
IE, no surprise, really... They cut features from haswell-K while charging more for it for example, for absolutely no other reason than that they can.
The annoying part is that its predecessors had 40 lanes for two generations now:
Core i7 3820: 40 lanes PCI-Express 2.0 at release price $294
Core i7 4820K: 40 lanes PCI-Express 3.0 at release price $310
Core i7 5820K: 28 lanes PCI-Express 3.0 at release price $390
The lower end of the LGA2011 platform used to be a good alternative to the higher-end of the LGA115x line.
Prices were similar, CPUs clocked somewhat better, much more PCI-Express lanes for upgrades and the socket lasted a lot longer.
I guess that wasn't interesting to Intel.
Bizarrely, h264 doesn't seem to scale to 16 threads, at least according to Tech Report: http://techreport.com/review/26977/intel-core-i7-5960x-processor-reviewed/10
They are talking about utilizing 16 threads, not frame scaling and filtering.That's because, for whatever reason, they chose to add scaling to x264's parameters. (Test one thing at a time people!).
x264's scaling filters are based on libswscale and is not multithreaded. As the TR folks are only testing `preset medium`, the multiple cores doing the actual encoding are chilling around waiting for the single core doing to the scaling. They might as well rename that specific benchmark to "single-threaded Bilinear scaling speed".
Handbrake uses x264 as its main encoder, so that's the more relevant benchmark.
They are talking about utilizing 16 threads, not frame scaling and filtering.
--video-filter resize:1280,720
I see, thanks. I guess I misunderstood.And the reason they are not utilizing 16 threads is that they have added
to their benchmark command line, which runs single-threaded frame scaling as part of the test. Should they remove that, the 16 cores would be well utilized.