Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ryzen Threadripper Pro 3995WX Spotted

guru3d.com

Post reply on HN
Print view View original

101–110 of 170 posts

Re: Ryzen Threadripper Pro 3995WX Spotted

#101

Post by satai »

Uehreka wrote: post #12

I feel like 64 cores is getting rather close to a tipping point: What workloads are so massively parallel that they can use 64 cores of x86 but can’t use the thousands of CUDA cores on a Quadro card? I’m sure right now there are workloads that just need particular x86 instructions, but that feels like a temporary problem. Am I wrong about that being a temporary problem (that would feel frustrating)? Are these cores j…

Almost anything, that doesn't move lots of data in lockstep (specially - anything with lots of it - then - elses) is much better to run on CPU cores.

Re: Ryzen Threadripper Pro 3995WX Spotted

#102

Post by elorant »

bobjordan wrote: post #35
Uehreka wrote: post #12

I feel like 64 cores is getting rather close to a tipping point: What workloads are so massively parallel that they can use 64 cores of x86 but can’t use the thousands of CUDA cores on a Quadro card? I’m sure right now there are workloads that just need particular x86 instructions, but that feels like a temporary problem. Am I wrong about that being a temporary problem (that would feel frustrating)? Are these cores j…

I'm using a 22 core / 44 thread xeon workstation for development and my primary joy using it is being able to run my pytest test suites in parallel. I went from ~45 minutes to run the test suite to about a minute. It is also pretty sweet to be able replicate our three physical servers for bomquote.com, locally.

Honest question because I'm interested for something similar, why did you go for a Xeon and not an Epyc rig?

Re: Ryzen Threadripper Pro 3995WX Spotted

#104

Post by behohippy »

CSDude wrote: post #41
vosper wrote: post #40

Earlier quoted context omitted.

I’m not sure about “require”, but we use multi-hundred-gigabytes or RAM instances for our Elasticsearch coordinator nodes, which seems to work well.

Elasticsearch recommends <32GB because of 32-bit per their doc, is it different for coordinator nodes?

A "perfect" ES node has 64 gig of memory. 32 to heap and 32 for off heap as well as 8-12 cores for executing queries. Heap is mostly used for internal operations and the inverted index stuff (fielddata), off-heap was used for the columnar data store (docvalues). Most server class machines exceed this nowadays, so we would recommend containerizing multiple instances of ES on a single machine and using the rack awareness feature to make sure shards didn't replicate onto the same physical host. It's been a while since I worked at Elastic, so this info might be out of date by now, but we're still using this formula for our ECE setups where I work now.

Re: Ryzen Threadripper Pro 3995WX Spotted

#105

Post by baybal2 »

ajross wrote: post #98
baybal2 wrote: post #96

Earlier quoted context omitted.

> Building software Well, the problem with that is that no make system can utilise so much core. Even linux kernel, probably the biggest C project in mainstream use, can not consistently load even 16 cores with mostly handwritten makefiles. P.S. I do not say that building software is not CPU parallelisable in principles, I'm saying that regular make systems have trouble handing big number of parallel tasks in practic…

That's... not true at all. A kernel build will be as parallelizable as you like. I do kernel builds fairly regularly on 56 and 64 core hosts and in fact the build time is quite linear with core count. (The ramdisk packing provided by the distro at "make install" time tends to be what hurts scaling, FWIW). And my day job involves lots of iterations over the Zephyr test suite, which builds and runs hundreds of individu…

Not in my experience, from time to time it does boost to 40+ compile tasks, especially on drivers code, but it mostly hover at around 10 tasks.

Re: Ryzen Threadripper Pro 3995WX Spotted

#106

Post by CrazyStat »

ajross wrote: post #98
baybal2 wrote: post #96

Earlier quoted context omitted.

> Building software Well, the problem with that is that no make system can utilise so much core. Even linux kernel, probably the biggest C project in mainstream use, can not consistently load even 16 cores with mostly handwritten makefiles. P.S. I do not say that building software is not CPU parallelisable in principles, I'm saying that regular make systems have trouble handing big number of parallel tasks in practic…

That's... not true at all. A kernel build will be as parallelizable as you like. I do kernel builds fairly regularly on 56 and 64 core hosts and in fact the build time is quite linear with core count. (The ramdisk packing provided by the distro at "make install" time tends to be what hurts scaling, FWIW). And my day job involves lots of iterations over the Zephyr test suite, which builds and runs hundreds of individu…

CPU-parallelizable and GPU-parallelizable are different problems. CPU cores are independent. GPU cores are SIMD--every core does the same operation, but with different data. That works really well for things like matrix multiplication where you need to multiply a million times and then add a million times, because you can have all 3000 CUDA cores multiplying and then all 3000 CUDA cores adding. It doesn't work for compiling software.

Re: Ryzen Threadripper Pro 3995WX Spotted

#107

Post by michaelt »

Uehreka wrote: post #12

I feel like 64 cores is getting rather close to a tipping point: What workloads are so massively parallel that they can use 64 cores of x86 but can’t use the thousands of CUDA cores on a Quadro card? I’m sure right now there are workloads that just need particular x86 instructions, but that feels like a temporary problem. Am I wrong about that being a temporary problem (that would feel frustrating)? Are these cores j…

> What workloads are so massively parallel that they can use 64 cores of x86 but can’t use the thousands of CUDA cores on a Quadro card?

Servers serving multiple independent requests, VMs or Docker containers.

In other words, the same thing people were doing with four 16-core servers, just now it takes up less space :)

Re: Ryzen Threadripper Pro 3995WX Spotted

#108

Post by jayflux »

pulse7 wrote: post #7
tpetry wrote: post #3

Earlier quoted context omitted.

Threadripper is the consumer line, epyc is for servers.

Refinement: Threadripper is for professional consumers.

Threadripper is the "enthusiast" level of the consumer line, I've seen many gamers buy Threadripper.

AMD use this term themselves.

Re: Ryzen Threadripper Pro 3995WX Spotted

#109

Post by Hello71 »

kllrnohj wrote: post #93
hellofunk wrote: post #68

It’s unclear to me what eight channel memory actually means, I’m not used to seeing that mentioned in casual architecture overviews. What’s the benefit of that? Is that something that a programmer must explicitly take advantage of, or is that just an automatic part of the CPU?

Think RAID 0 but for RAM done by the CPU. Nearly every consumer CPU for the last 20 years is dual channel, meaning "2 drive RAID 0". If you've seen things like recommendations to get paired DDR memory sticks, this is why. You only get this RAID-like benefit with multiple RAM sticks (just like RAID 0 of a single drive doesn't do anything). It's also why some consumer products have unexpectedly bad performance for the…

also notably this doesn't help with latency, which is more often the sticking point.

Re: Ryzen Threadripper Pro 3995WX Spotted

#110

Post by Roritharr »

kllrnohj wrote: post #91
Roritharr wrote: post #23

I wonder how much the silicon quality differs on a single Threadripper Chip. It would really be interesting to see if it's feasible to Overclock the best numa node to a degree that gives this a couple of high single thread performance cores comparable to the 3900X or 3950X while retaining stability overall.

> Overclock the best numa node to a degree Do you mean the best ccx? Or best chiplet? There aren't any numa nodes here, and the cache & memory architecture are already the same as a 3900x. Per-core & per-ccx overclocking does already exist on ryzen though, should work the same on threadripper.

Interesting, is it already feasible to pin tasks to such OCed cores?

It would be interesting to turn the 3990/3995 into a does-it-all chip with best in class single-core performance on certain cores and just lots of a tad slower cores in general.

Post reply on HN