AVX512 vs Threadripper in x265

[K.i.N.G]

Im currently looking to buy a new render/encoding system.

I can't decide if I should get the threadripper 1950x or the i9 7900x... Looking at several benchmarks and reviews, Threadripper seems to perform really well overall, but what is making me doubt is the lack of AVX512 support.

Since I'm also going to offload a lot of 3D rendering to this system it might be important, but it's hard to tell because I currently I don't know any rendering software that already has AVX512 support.
So I cant find any benchmarks that show me how much of a difference it'll make.

I've always hold off buying a new system because I read how much difference AVX512 could potentially make...

But looking at x265's AVX512 results posted here it seems not to be really worth it... Or might that be because the AVX512 code is not fully ready/optimized yet (considering its only recently added)?

Also, a bit off topic but 3D rendering (ray-tracing) is totally different so I'm wondering how much of a difference AVX512 can make there... (currently no renderer supports it so I have no clue since I know nothing about coding, instruction sets and related maths).

ahhhrgh choices choices....

[mandarinka]

From what I remember from the benchmarks, Zen (and thus Threadripper) has some of its strongest results in 3d rendering. It's probably suited it for it even better than for encoding.

If you are not in hurry, you might want to wait till august, that's when the second generation should launch. And in second half of the year, Intel should have i9-7900X replacement too.

On the other hand, now you can get discounts on the current generation, although mainly in USA.

[foxyshadis]

AVX512 is so badly memory and power bound that x265 can rarely use it effectively. For power, that means tweaking the BIOS and having a very solid cooling solution lined up, because I've heard of AVX512 alone exceeding 300W in unrestricted environments, in addition to the rest of the CPU and system, and for memory, that basically means buying the biggest i9 you can afford (since more cores = more cache = lower latency). Short of that, the investment probably isn't worth it.

[NikosD]

I can't decide if I should get the threadripper 1950x or the i9 7900x... Looking at several benchmarks and reviews, Threadripper seems to perform really well overall, but what is making me doubt is the lack of AVX512 support.

ahhhrgh choices choices....

I can make your life easy.

You have no choice. Nothing. Nothing at all.

Between 7900x and 1950x you can only buy one processor and that is of course 1950x or 2950x that will be released at Q3 2018.

The overall difference, as you already know, is huge favoring 1950x especially on rendering/ encoding and AVX512 is nonsense, pure nonsense for almost any task for desktop or even workstation.

You need 6 channel or 8 channel DDR4 or maybe DDR5 (2019/2020) to leverage effectively AVX512 and water cooling in most cases.

Let's forget AVX512 for the next 5 years for desktop and workstation.

[hajj_3]

I'd wait a few months for next gen threadripper.

[RanmaCanada]

Im currently looking to buy a new render/encoding system.

I can't decide if I should get the threadripper 1950x or the i9 7900x... Looking at several benchmarks and reviews, Threadripper seems to perform really well overall, but what is making me doubt is the lack of AVX512 support.

Since I'm also going to offload a lot of 3D rendering to this system it might be important, but it's hard to tell because I currently I don't know any rendering software that already has AVX512 support.
So I cant find any benchmarks that show me how much of a difference it'll make.

I've always hold off buying a new system because I read how much difference AVX512 could potentially make...

But looking at x265's AVX512 results posted here it seems not to be really worth it... Or might that be because the AVX512 code is not fully ready/optimized yet (considering its only recently added)?

Also, a bit off topic but 3D rendering (ray-tracing) is totally different so I'm wondering how much of a difference AVX512 can make there... (currently no renderer supports it so I have no clue since I know nothing about coding, instruction sets and related maths).

ahhhrgh choices choices....

Agree with Nikos. Threadripper is your only option, really. Intel's chips are too power hungry, and for the price, not worth it. You would need a ridiculous cooling system and power delivery to maintain loads that Threadripper can handle 24-7. Either get one now, or wait till Q3 and the new ones drop..or get an old one at a discount.

AVX512 is not going to make a difference for at least another 3-4 generations, IF that.

[K.i.N.G]

ok, thanks for the help guys... You helped me make up my mind
I think i'll wait a little longer until Q3-Q4. I can imagine i'd be quite disappointed to invest that amount of money for something that will be updated/replaced only in a month or 5-6.

[Selur]

I can imagine i'd be quite disappointed to invest that amount of money for something that will be updated/replaced only in a month or 5-6.
I can't really imagine that this isn't what you need to expect when buying pcs. ;)

[divxmaster]

ok, thanks for the help guys... You helped me make up my mind
I think i'll wait a little longer until Q3-Q4. I can imagine i'd be quite disappointed to invest that amount of money for something that will be updated/replaced only in a month or 5-6.

And of course the 9700k? should support AVX512 also.

- Well after getting my 8700k yesterday, I finally see what everyone is talking about with core saturation. I'm only getting about 66% cpu use, with moderate vsynth + x265. (576p so far)
Am I correct that the best way around this is to run two encodes at the same time?

Cheers,
Divxmaster

[Asmodian]

Yes, two encodes at once. Also larger resolutions and slower settings utilize more cores effectively.

[Atak_Snajpera]

ok, thanks for the help guys... You helped me make up my mind
I think i'll wait a little longer until Q3-Q4. I can imagine i'd be quite disappointed to invest that amount of money for something that will be updated/replaced only in a month or 5-6.

Or wait again until mid 2019 for threadripper (24C/48T) with better AVX unit in 7nm...

[divxmaster]

Yes, two encodes at once. Also larger resolutions and slower settings utilize more cores effectively.

Thanks, yes you are 100% correct, just tried with 1920x800 and it is using 95-100% all cores. Oh well, guess will use my 4770k for SD and my 8700k for FHD - when my new MB for 4770k arrives as old one blew up :(

Cheers,
Divxmaster

[Atak_Snajpera]

Thanks, yes you are 100% correct, just tried with 1920x800 and it is using 95-100% all cores. Oh well, guess will use my 4770k for SD and my 8700k for FHD - when my new MB for 4770k arrives as old one blew up :(

Cheers,
Divxmaster

If you have two pcs at home then why don't you use them in Distributed Encoding mode? This way you can save a lot of encoding time.

Regarding AVX-512.
Is it me or implementation of AVX-512 in x265 was a waste of time?
https://networkbuilders.intel.com/docs/accelerating-x265-the-hevc-encoder-with-intel-advanced-vector-extensions-512.pdf

"for server-grade CPUs that have the Intel
AVX-512 instructions, this acceleration should be used only
for certain profiles of x265 that focus on encoding high
resolution video (4K and higher) in the main10 profile using
the slower or veryslow presets due to the impact that the
Intel AVX-512 instructions have to clock frequency. For other
profiles on server CPUs with Intel AVX-512 instructions,
enabling these kernels is not recommended."

[foxyshadis]

x265 must have clients who would use slow/veryslow 4K on heavy-duty server cpus, or they wouldn't have bothered -- I imagine Netflix is the main buyer of that feature.

[divxmaster]

If you have two pcs at home then why don't you use them in Distributed Encoding mode? This way you can save a lot of encoding time.

Thx Atak,
yes I also have ripbot264 as an option, I've had a quick play with it.

Cheers,
Divxmaster

[WhatZit]

Is it me or implementation of AVX-512 in x265 was a waste of time?

I'm noticing a pervading impression that MulticoreWare are only developing x265 for "enthusiast" users, when they are, in fact, developing it as part of a platform for professional/commercial content creators.

Consumers are merely enjoying the consequences of the base encoder being open-source. Most of MCW's HEVC products are propietary.

Specifically regarding AVX512, see here:
https://www.intel.com.au/content/www/au/en/processors/xeon/scalable/software-solutions/multicoreware-comms-uhdkit.html

So, if you don't want to rapidly encode 20 target variations of the one master source, don't have the requisite farm of US$10000 server processors, don't want to encode 4:2:2 4K60 in real-time, or don't actually even use UHDKit (which, I'm guessing, cleverly compartmentalises AVX512 API workloads), then it's easy to dismiss the last year's worth of development as wasted.

[Sagittaire]

If you have two pcs at home then why don't you use them in Distributed Encoding mode? This way you can save a lot of encoding time.

Regarding AVX-512.
Is it me or implementation of AVX-512 in x265 was a waste of time?
https://networkbuilders.intel.com/docs/accelerating-x265-the-hevc-encoder-with-intel-advanced-vector-extensions-512.pdf

Really interessing document.

Well I thing that gain in 1080p resolution are realistic. 7900X is 10C/20T CPU. x265 in 1080p can't saturate 8C/16T CPU. 1080p for 8C/16T is something like 60-70% for CPU charge. In this case, no power problem here, and no offset for frequency are necessary (real power will be under TDP).

[LigH]

IMHO, implementing it was not a waste of time because theory promised the existence of hardware and usage cases where the efficiency advantage could be considerable; but you can't be sure until proven (either right or wrong) by practical tests. And who knows the future ... I won't be surprised if the implementation in x265 may help the designers of coming CPU generations to avoid flaws of the previous.

[The Stilt]

I can make your life easy.

You have no choice. Nothing. Nothing at all.

Between 7900x and 1950x you can only buy one processor and that is of course 1950x or 2950x that will be released at Q3 2018.

The overall difference, as you already know, is huge favoring 1950x especially on rendering/ encoding and AVX512 is nonsense, pure nonsense for almost any task for desktop or even workstation.

You need 6 channel or 8 channel DDR4 or maybe DDR5 (2019/2020) to leverage effectively AVX512 and water cooling in most cases.

Let's forget AVX512 for the next 5 years for desktop and workstation.

Unless we're talking strictly about encoding material with > 1080 vertical resolution or running multiple encoder instances simultaneously, Threadripper is is pretty much the worst possible choice for HEVC encoding you can currently get.

Skylake-X has > 50% IPC advantage in the most recent encoder version over Ryzen, due to AVX2 (+41.7%) and AVX512 (+6.1%). Obviously Skylake-X is expensive and the power consumption is rather brutal, but regardless for typical end-user scenarios you're better basically with anything else than Threadripper. On a budget used MCC or HCC Haswell-EP CPUs are probably the best way to go.

[user1085]

Skylake-X has > 50% IPC advantage in the most recent encoder version over Ryzen, due to AVX2 (+41.7%) and AVX512 (+6.1%). Obviously Skylake-X is expensive and the power consumption is rather brutal, but regardless for typical end-user scenarios you're better basically with anything else than Threadripper. On a budget used MCC or HCC Haswell-EP CPUs are probably the best way to go.

I'm not seeing these gains with my AVX512 testing. Can you check if I have the right CLI options?

https://forum.doom9.org/showthread.php?t=175467

[NikosD]

Unless we're talking strictly about encoding material with > 1080 vertical resolution or running multiple encoder instances simultaneously, Threadripper is is pretty much the worst possible choice for HEVC encoding you can currently get.

Skylake-X has > 50% IPC advantage in the most recent encoder version over Ryzen, due to AVX2 (+41.7%) and AVX512 (+6.1%). Obviously Skylake-X is expensive and the power consumption is rather brutal, but regardless for typical end-user scenarios you're better basically with anything else than Threadripper. On a budget used MCC or HCC Haswell-EP CPUs are probably the best way to go.

There are no such things you describe, like IPC advantage or single instance encoding or even encoding below 1080p .

You seem desperate to prove Threadripper is lame compared to Skylake-X, by manipulating the user conditions.
Do you really think that the IPC advantage of a CPU has anything to do with a 10C/20T vs 16C/32T comparison ?

At the end of the day we are comparing final products and not just architectures at very specific situations.

Because those two CPUs have the same price.

Skylake-X is a choice for Intel's fanboys or for people who can afford burn money in the fireplace during the winter.

[The Stilt]

There are no such things you describe, like IPC advantage or single instance encoding or even encoding below 1080p .

You seem desperate to prove Threadripper is lame compared to Skylake-X, by manipulating the user conditions.
Do you really think that the IPC advantage of a CPU has anything to do with a 10C/20T vs 16C/32T comparison ?

At the end of the day we are comparing final products and not just architectures at very specific situations.

Because those two CPUs have the same price.

Skylake-X is a choice for Intel's fanboys or for people who can afford burn money in the fireplace during the winter.

"There are no such things" can you elaborate a bit on that?

I have both, the 7960X and 1950X.
Even if I had only the 7900X, I'd still use it for HEVC encoding rather than the 1950X due to speed and higher efficiency.

https://images.anandtech.com/graphs/graph11839/91525.png

https://images.anandtech.com/doci/11839/hb_efficiency_575px.png

Obviously in other multithreaded workloads the 1950X will annihilate the 7900X, but that's not the case with X265.

I'm not seeing these gains with my AVX512 testing. Can you check if I have the right CLI options?

https://forum.doom9.org/showthread.php?t=175467

Have you monitored the average clock frequency of the CPU cores between AVX2 and AVX512 options? At least on my 7960X the current AVX512 implementation in X265 does not trigger the AVX512 clock offset, however I'm not certain if the rules are the same for Xeons as well. I'd suggest you limit the encoder threads to a lower number (e.g. 8, --pools "8") and test again. At 205W power limit and 24 cores you are definitely hitting the power limits, which causes high variation in the frequency. Also, try using a raw YUV input (file) for the encoder, instead of piping the video from ffmpeg.

[Sagittaire]

"There are no such things" can you elaborate a bit on that?

I have both, the 7960X and 1950X.
Even if I had only the 7900X, I'd still use it for HEVC encoding rather than the 1950X due to speed and higher efficiency.


Annand tech bench is simply stupid and ridiculous test:
- 4K HEVC source at very high bitrate (~140 fps at 100% CPU charge just for stream decoding on i9-7900X and 1950X ... and Intel is really better than AMD for that)
- Really high speed setting (40 fps and more for 4K x265 encoding ... !!!?).

Certainely that Handbrake use high CPU charge just for 4K HEVC decoding source.

I make more serious bench here with 4K source and x265 encoding with preset "medium":
https://forum.doom9.org/showthread.php?t=174393


|----------------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|--------|
| CPU | x264 | x265 | LAVC | auto | MMX2 | SSE | SSE2 | SSE3 | SSE4 | AVX | AVX2 | All |
|----------------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|--------|
| 1950X | 37.59 | 6.50 | 136 | 4.65 | 2.02 | 2.00 | 2.95 | 3.10 | 3.89 | 4.10 | 4.26 | N/A |
| Core i9-7900X | 29.37 | 5.47 | 145 | 4.38 | 1.35 | 1.35 | 2.14 | 2.32 | 3.49 | 3.50 | 4.30 | N/A |


For real x265 encoding (less than 5% on CPU charge for source decoding):
- 1950x@stock 16C/32T is faster than i9-7900x@stock 10C/20T for x265 4K encoding.
- SSE4 at same speed and same core number is on par for Intel and AMD for x265 encoding.
- AVX2 produce 15-20% speed improuvement for Intel vs AMD in x265 encoding (on all modern CPU)
- AVX2 is not really efficient for x264: at same speed and same core number Intel and AMD are on par for speed encoding.

[jd17]

There is one point from @The Stilt that still might stand:
Efficiency.

It seems to me like some in this forum consider speed only.

I am not sure about this particular case, because I have neither of these high-end CPUs, but I investigated a lot before I bought my current CPU.

If the Intel is slower, but still uses less power over the entire encoding time, it is the more efficient CPU and should be the better choice at the same price - at least for someone who does a lot of encoding.
At the end of the day - it would be cheaper to run.

Again, I am not saying this is the case here, I simply don't know.

I bought a Kaby Lake CPU back in the day and I looked at most of the lineup from G4560 to i7-7700K.
Between these CPUs, the most efficient ones were i5-7400 and i5-7500, both non-HT Quads. Neither the cheapest, nor the fastest - but the most efficient, so the cheapest to run.
I ended up buying an i5-7500...

[Atak_Snajpera]

Annand tech bench is simply stupid and ridiculous test:
- 4K HEVC source at very high bitrate (~140 fps at 100% CPU charge just for stream decoding on i9-7900X and 1950X ... and Intel is really better than AMD for that)
- Really high speed setting (40 fps and more for 4K x265 encoding ... !!!?).

Certainely that Handbrake use high CPU charge just for 4K HEVC decoding source.

I make more serious bench here with 4K source and x265 encoding with preset "medium":
https://forum.doom9.org/showthread.php?t=174393


|----------------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|--------|
| CPU | x264 | x265 | LAVC | auto | MMX2 | SSE | SSE2 | SSE3 | SSE4 | AVX | AVX2 | All |
|----------------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------|--------|
| 1950X | 37.59 | 6.50 | 136 | 4.65 | 2.02 | 2.00 | 2.95 | 3.10 | 3.89 | 4.10 | 4.26 | N/A |
| Core i9-7900X | 29.37 | 5.47 | 145 | 4.38 | 1.35 | 1.35 | 2.14 | 2.32 | 3.49 | 3.50 | 4.30 | N/A |


For real x265 encoding (less than 5% on CPU charge for source decoding):
- 1950x@stock 16C/32T is faster than i9-7900x@stock 10C/20T for x265 4K encoding.
- SSE4 at same speed and same core number is on par for Intel and AMD for x265 encoding.
- AVX2 produce 15-20% speed improuvement for Intel vs AMD in x265 encoding (on all modern CPU)
- AVX2 is not really efficient for x264: at same speed and same core number Intel and AMD are on par for speed encoding.

I see similar results for 1080p as well.
https://i.imgur.com/ShtyZ2q.png

[RanmaCanada]

I'd take both Sagittare's benchmark and Atak's words over some random's Anandtech/Intel worshiping. Anandtech hasn't been impartial for years and nothing on their p"review" site can be trusted. Heck none of the review sites properly use x265 in their benchmarks.

And let's be clear. The 7900x (http://www.guru3d.com/articles-pages/intel-core-i9-7900x-processor-review,5.html)uses far more power than the 1950x (http://www.guru3d.com/articles-pages/amd-ryzen-threadripper-1950x-review,8.html).

TDP doesn't mean anything if you can't stick to it.

[Asmodian]

At 4.0 GHz (max OC) the 1950X uses a lot more power than at stock, just like the 7900X (https://www.gamersnexus.net/hwreviews/3015-amd-threadripper-1950x-1920x-review/page-4). The 1950X does use a little less power in most situations but it isn't a major difference, 16 cores v.s. 10. Power numbers can move around a lot too, depending on the motherboard (voltages and exact power saving options chosen).

Also, it is hard to saturate 16 cores with 1080p encodes. There are times when 10 faster cores are better.

The 1950X is a great CPU for encoding but it is hardly so black and white, the 7900X is great too. For pure x265 price/performance easily goes the the 1950X but it is slower in many situations and not that much more efficient.

[Atak_Snajpera]

If you do some extra filtering in avisynth (Resize from 2160p to 1080p + HDRtoSDR tone mapping + MDegrain denoising) then saturating all 32 threads in Threadripper won't be a problem.
My example script I use while encoding UHD HDR to FHD SDR
#MT
Import("C:\Users\Dave\Documents\Delphi_Projects\RipBot264\_Compiled\Tools\AviSynth plugins\Scripts\MTmodes.avs")
#PREFETCH_LIMIT=0

#VideoSource
LoadPlugin("C:\Users\Dave\Documents\Delphi_Projects\RipBot264\_Compiled\Tools\AviSynth plugins\ffms\ffms_latest\x64\ffms2.dll")
video=FFVideoSource("E:\_Video_Samples\mkv\Passengers_2016_4K.mkv",cachefile = "C:\Temp\RipBot264temp\job1\Passengers_2016_4K.mkv.ffindex")

#Crop
video=Crop(video,0,278,-0,-278)

#Resize
LoadPlugin("C:\Users\Dave\Documents\Delphi_Projects\RipBot264\_Compiled\Tools\AviSynth plugins\Plugins_JPSDR\Plugins_JPSDR.dll")
video=Spline36ResizeMT(video,1920,800,SetAffinity=false).Sharpen(0.2)

#Tonemap
Loadplugin("C:\Users\Dave\Documents\Delphi_Projects\RipBot264\_Compiled\Tools\AviSynth plugins\avsresize\avsresize.dll")
Loadplugin("C:\Users\Dave\Documents\Delphi_Projects\RipBot264\_Compiled\Tools\AviSynth plugins\DGTonemap\x64\DGTonemap.dll")
video=z_ConvertFormat(video,pixel_type="RGBPS",colorspace_op="2020ncl:st2084:2020:l=>rgb:linear:2020:l", dither_type="none").DGHable
video=z_ConvertFormat(video,pixel_type="YV12",colorspace_op="rgb:linear:2020:l=>709:709:709:l",dither_type="ordered")

#Denoise
Loadplugin("C:\Users\Dave\Documents\Delphi_Projects\RipBot264\_Compiled\Tools\AviSynth plugins\mvtools\mvtools2.dll")
super=MSuper(video,pel=2)
fv1=MAnalyse(super,isb=false,delta=1,overlap=4)
bv1=MAnalyse(super,isb=true,delta=1,overlap=4)
fv2=MAnalyse(super,isb=false,delta=2,overlap=4)
bv2=MAnalyse(super,isb=true,delta=2,overlap=4)
video=MDegrain2(video,super,bv1,fv1,bv2,fv2,thSAD=400)

#Prefetch
video=Prefetch(video,8)





In this case Threadripper will just crush 7900x.

[Asmodian]

It is not that I believe you are wrong, I don't have great data here, but what does "crush" mean in terms of actual percentage performance difference? People tend to be way too.. sure.. of their CPU choices without a lot of data to back it up.

The 1950X is a great CPU for encoding, I would absolutely recommend to anyone building an encoding box on a budget, but I haven't seen any good data which shows it "crush" the 7900X in a encoding workload (e.g. a 4K x265 encode) or the 7900X using "far more power" when the 1950X is actually matching or out performing the 7900X. $/performance is not a contest but raw performance is a lot closer.

What kind of FPS numbers do you get with the 1950X, and what does a 7900X get? Any data on power use for both systems? :o

The limited reviews posted in this thread, and what I have found elsewhere, use different workloads and have results with differences small and varied enough it is hard to draw any definitive conclusions from them. We know it is hard to saturate both CPUs and saturation has a big impact on both performance and power use. I would not be surprised to see some crushing in well threaded workloads, the 1950X has 60% more cores and each core is not that much slower. I just haven't seen any benchmarks which show it, I suspect this is because reviewers never use encoding options or workflows which properly saturate the 1950X, but this would also cause its power numbers to be lower. Some data would be great. :p

[Atak_Snajpera]

7900X shines in x265 due to superior AVX2 unit (2 times wider). However most filters I use do not use AVX2 at all! This means that CPU will be spending more time executing non AVX code (In most cases plain SSE2 code) than AVX2. So speed advantage on x265 side will shrink significantly. Just take a look how many cpu cycles decoding process (ffmpeg.exe) eats using above script on my E5-2690 (8C/16T).

https://s15.postimg.cc/rw9zpyapn/Untitled-1.png

[RanmaCanada]

It is not that I believe you are wrong, I don't have great data here, but what does "crush" mean in terms of actual percentage performance difference? People tend to be way too.. sure.. of their CPU choices without a lot of data to back it up.

The 1950X is a great CPU for encoding, I would absolutely recommend to anyone building an encoding box on a budget, but I haven't seen any good data which shows it "crush" the 7900X in a encoding workload (e.g. a 4K x265 encode) or the 7900X using "far more power" when the 1950X is actually matching or out performing the 7900X. $/performance is not a contest but raw performance is a lot closer.

What kind of FPS numbers do you get with the 1950X, and what does a 7900X get? Any data on power use for both systems? :o

The limited reviews posted in this thread, and what I have found elsewhere, use different workloads and have results with differences small and varied enough it is hard to draw any definitive conclusions from them. We know it is hard to saturate both CPUs and saturation has a big impact on both performance and power use. I would not be surprised to see some crushing in well threaded workloads, the 1950X has 60% more cores and each core is not that much slower. I just haven't seen any benchmarks which show it, I suspect this is because reviewers never use encoding options or workflows which properly saturate the 1950X, but this would also cause its power numbers to be lower. Some data would be great. :p

You apparently missed the benchmark results that were posted by Sagittare, which uses the same work load, and the same file across every single cpu that is benchmarked. In 4k the 1950x beat the 7900x by 1fps, on medium.

But let's face it, until x265 can saturate more than 10? threads, the only real way to test it is to own both, and run multiple instances at the same time :P

[Asmodian]

:confused:x265 can easily saturate 20 threads on veryslow.

And I don't see any benchmarks from Sagittare that show a big performance difference and everything in this thread seems to show the 7900X is slightly faster?

What did I miss? :o

Oh, wait I think I see. The "x265" column, I maybe don't understand what the AVX, AVX2, etc. columns are benchmarking. :confused:

[NikosD]

Shock and Awe !

Threadripper 2000 is a 32C/64T absolute monster at 250W TDP, compatible with X399 motherboards coming on August.

It's a nuke on the head of Intel:

https://www.anandtech.com/show/12906/amd-reveals-threadripper-2-up-to-32-cores-250w-x399-refresh

[RanmaCanada]

Now if the price points are the same as the previous generation, this will destroy Intel's market share and everyone will have a Threadripper :P. I can't wait for this to be released. Hopefully this time we will get some real proper reviews on work loads as this goes beyond HEDT and steps into workstation/server territory.

[NikosD]

It seems that Intel will answer that 24C/48T Threadripper with a 22C/44T chip belonging to Skylake HCC (High Core Count), a special chip because max cores of HCC are 18C/36Τ, that could be used on existing X299 motherboards a month or two after Threadripper 2 release.

No clocks, TDP or price is available.

But for 32C/64T there is no answer.

There will be a response at the end of the year or early 2019 in the form of a new chipset/ board and a new CPU (Cascade Lake-X) reaching 28C/56T.

But that could be extremely expensive and probably not worth its money, like most of the Intel CPUs nowadays.

[nevcairiel]

Intel HCC is a 4x5 grid layout with 2 memory controllers, so 18 CPU cores max. They can't just make a new 22 core chip without re-engineering the Die, which would basically be an entirely new CPU line.

[Asmodian]

It is from their XCC line.

[NikosD]

Guys, I had the same thoughts until I read that:

https://www.techpowerup.com/245090/intel-readying-22-core-lga2066-and-8-core-lga1151-processors

[nevcairiel]

Well the article says that it's not HCC but a new die. Seems unusual to me, I don't think they would sell enough of those to actually make it worth creating a new in-between die.

[NikosD]

It's a new die, I called it a special case of HCC, Intel should name it differently but definitely it's not a new CPU or a new CPU architecture.

[LigH]

P.S.: Someone just had to ...

https://frupic.frubar.net/shots/37287.jpg