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

121–130 of 170 posts

Re: Ryzen Threadripper Pro 3995WX Spotted

#121

Post by kevin_thibedeau »

throwaway_pdp09 wrote: post #60
secondcoming wrote: post #54

Earlier quoted context omitted.

The impending doom that is WASM will mean that 'dynamic' and 'interactive' adverts will use all these cores.

What a miserable hopeless post - "they're going to fuck us and what can we do????". Answer: quite a lot, if you have even minimal technical understanding (like, enough to use a blocklist or an ad blocker). Are you incapable even of that?

Your ad blocker is going to filter a private web socket link funneling ads and content together? It's going to patch the WASM?

Re: Ryzen Threadripper Pro 3995WX Spotted

#122

Post by raphlinus »

scotty79 wrote: post #87
ajross wrote: post #85

Earlier quoted context omitted.

> 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? Building software, for one. C compilers and python interpreters don't run on a GPU. Lots of stuff doesn't run on a GPU. In fact in practice the only things that run on a GPU are the tiny handful of known subproblems that the industry has collectively decided are "GPU problems". Like…

Interesting. Is there a compiler, that runs on GPU?

A really interesting exploration is Co-dfns [1]. This is indeed a compiler that runs on the GPU, but it's also extremely out of the mainstream.

IMHO this is an area ripe for more exploration. If I were working on it, I might look to linking first before compilation, because the basic link task is more similar to what GPUs are good at (advanced stuff such as LTO is a different story, though).

[1]: https://github.com/Co-dfns/Co-dfns

Re: Ryzen Threadripper Pro 3995WX Spotted

#123

Post by gameswithgo »

Hello71 wrote: post #109
kllrnohj wrote: post #93

Earlier quoted context omitted.

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.

with 64 cores and 4 channels, throughput may often be a sticking point.

that is like have 32 cores on a normal 2 channel desktop, throughput would often be a limiter there.

Re: Ryzen Threadripper Pro 3995WX Spotted

#124

Post by cptskippy »

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…

> Are these cores just that much faster than CUDA cores? What else am I missing here?

Comparing GPU/CUDA/TPU Cores to CPU Cores is like comparing a riding lawnmower to an automobile. A GPU/CUDA/TPU Core is optimized to handle a different type of workload than a CPU.

Just because your riding lawnmower can cut your grass faster than your car, doesn't mean your lawnmower is the best thing for highway driving.

Re: Ryzen Threadripper Pro 3995WX Spotted

#125

Post by secondcoming »

CyberDildonics wrote: post #115
secondcoming wrote: post #54

Earlier quoted context omitted.

The impending doom that is WASM will mean that 'dynamic' and 'interactive' adverts will use all these cores.

wasm can only do what javascript can already do, but faster. What specifically do you think wasm will change?

Threads. There's going to be a lot of 'throw threads at it and hope performance issues go away'-type solutions.

https://github.com/WebAssembly/proposals/issues/14

Re: Ryzen Threadripper Pro 3995WX Spotted

#126

Post by smichel17 »

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…

My understanding of these problems is totally naive, but I wonder if you could mitigate speculative execution vulnerabilities (meltdown, spectre, yes I know the former does not apply to amd) by using the excess cores to speculate enough that a cache hit is no longer meaningful data.

Re: Ryzen Threadripper Pro 3995WX Spotted

#127

Post by Symmetry »

the_pwner224 wrote: post #90
scotty79 wrote: post #87

Earlier quoted context omitted.

Interesting. Is there a compiler, that runs on GPU?

GPUs are mainly good at doing matrix multiplication and other math with little branching. Compilers have a lot of if/else statements; training neural networks does not. IIRC (and I may be wrong) the architecture is something like many GPU cores share things like the code cache and branch prediction, so if the different cores have to execute different code paths there is a big performance decrease. Edit: another reply…

Also GPUs really like predictable memory access patterns so that they can load the data that'll be needed next ahead of time into registers or dedicated caches explicitly. They don't have cache hierarchy features a CPU has to minimize the average disruption from only partially predictable memory accesses and they don't have out of order windows to paper over the occasional low level cache miss.

Re: Ryzen Threadripper Pro 3995WX Spotted

#128

Post by hyperbovine »

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 see this response often and I have to say, "just throw it on the GPU" is phrase only uttered by someone who has never personally attempted to do that. The simplicity of CUDA and `pip install tensorflow-gpu` belie a huge amount of engineering prowess; go look at the source for XLA (https://github.com/tensorflow/tensorflow/tree/master/tensorf...) if you don't believe me. To answer your question, tons of scientific computing tasks parallelize nicely and are a horrible fit for a GPU, because they involve branching, or non-deterministic runtimes, or need a lot of memory bandwidth, or rely on highly optimized legacy numerical code that is written in Fortran, or any one of a number of other reasons. Deep learning is a very narrow use fact and, in fact, GPUs and DL symbiotically co-evolved over the last 15 years to the point where GPU hardware is essentially designed to efficiently train neural nets. (And run games.)

Re: Ryzen Threadripper Pro 3995WX Spotted

#129

Post by monocasa »

CrazyStat wrote: post #106
ajross wrote: post #98

Earlier quoted context omitted.

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 co…

It's not that SIMD for GPUs. It'll be 64 or 32 GPU threads together generally sharing the dispatch and control logic. So if you have a 4096 "CUDA core" GPU, it'll be 64 of what would be called cores on the CPU side, each with a 64 lane vector processor.

Re: Ryzen Threadripper Pro 3995WX Spotted

#130

Post by johncalvinyoung »

secondcoming wrote: post #125
CyberDildonics wrote: post #115

Earlier quoted context omitted.

wasm can only do what javascript can already do, but faster. What specifically do you think wasm will change?

Threads. There's going to be a lot of 'throw threads at it and hope performance issues go away'-type solutions. https://github.com/WebAssembly/proposals/issues/14

As someone working with cutting-edge CAD in the browser, I badly want to throw more threads at problems.
Post reply on HN