What does /g/ needs his Threadripper for?
>>107748478I would only ever use gentoo if I had one of these
>>107748478What does anyone need them for? Usecase?
>>107748611Workstations, presumably. Hardware manufacturers are still pretending that segment exists despite sales being in the triple digits for like a decade now.
>>107748677What kind of workstation, what's being done on it?
>>107748478chat is this real?
Threads are honestly still way ahead of their time despite the fact that they should be figured out as of 20+ years ago. GPUs have completely stolen the spotlight but only because they are relatively easy to program. A lot of posers like to larp like they know how to do multithreaded programming and it's not that hard etc but truth of the matter is nobody has delivered on that promise besides operating system kernels, user space is a complete mess and it might be on purpose. Truth of the matter is that the use case for highly performant threads is restricted to absolute retard tier implementations of like servers and virtual machines, nothing actually useful at the application layer. A testament to how absolutely difficult it is to get right. It's still just a matter of time perhaps, but it will take more than just effort, divine intellect is needed.
>>107748611>>1077486923D rendering, multiple VMs, containers, automating bots, etc
>>107748478Compiling C++. At work I have 7950x and it takes 10 minutes to fresh build the project I work on - and that is just 3M LoC.
>>107748692Capital W Workstation. Not your gayming desktop. They were up to 100x more powerful than personal microcomputers around the turn of the millenium and would run Unix while home desktops ran DOS. Rendered early Pixar movies and stuff. The segment doesn't really exist anymore because all use-cases are better handled by desktops or rack servers with how hardware has progressed and slowed progressing.>>107748862When you have that many threads, applications' inability to use them is more from Amdahl's law than programmer incompetence. Only embarrassingly parallel applications could ever hope to use more than 4-6 threads or run on the GPU. That's why SIMD and very wide AVX is so important, they can solve a hell of a lot more problems, and also using them is more commonly a benefit due to the lower overhead. Ideally you'd do both of course but again, Amdahl. That's why server CPUs are for you know... servers. You can only use the cores by doing multiple things or the same thing multiple times.
running 2 electron programs
>>107748478Mining Monero for negative profit
>>107748478>no m.2 >no satawut
>>107749293Photoshop and Premiere are also optimised for multithreading
>>107748478Running a bunch of virtual machines to remotely access elsewhere around the house.
>>107750015m.2 on the back.Maybe SATA, too, but probably not.
>>107748611Imagine the boot times. Wow.
