5 ms·
I've played with the AMD Daytona Rome Server (two EPYC sockets, 2*64 = 128 cores, 256 threads), with RHEL, and it rocks. However it's quite hard to find worklo
by rwmj 7y ago
I've played with the AMD Daytona Rome Server (two EPYC sockets, 2*64 = 128 cores, 256 threads), with RHEL, and it rocks. However it's quite hard to find workloads that keep all 256 threads busy at once. Most builds aren't nearly parallel enough, most programs can't find work for 256 threads. So as a personal machine 128 or 256 threads aren't really worth it unless money is no object. Likely the best current use for these is as servers for running large numbers of virtual machines or containers.
- tn890 7y agoMaking it an ESXi host would be the obvious solution.
- nineteen999 7y agoBlender's Cycles renderer would also eat those cores for lunch with a detailed enough scene.
- anon73044 7y agoAnd get raked over the coals with vmWare's new per core license update? Only quad channel? Only 256gb of ram supported? A pair of used 7601s, motherboard, ram, power supply and chassis would still be cheaper for a SOHO setup.
- glangdale 7y agoI am craving one of these for my superoptimizer. The level of task parallelism I have is north of 100M independent jobs; my last run took a single-core machine 20 days. It's pretty rare to have a workload like this but as more machines ship with >16 cores, I think more developers will look at the order-of-magnitude improvements of parallelizing their tasks where possible.
- qubex 7y agoOf course, not everything can be parallelised.
- namibj 7y agoIn what context are you working with Superoptimizers, if you don't mind me asking?
- Straw 7y agoCan you tell us more about this superoptimizer?
- glangdale 7y agoIt's an SMT-based solver to make fast "single-lane" SIMD calculations for AVX2 (doing different things in multiple lanes, doing AVX512 or SSE or ARM or general purpose registers, etc. are all on my todo list). Branch free code only. Can handle up to 4 or 5 instruction sequences including things like generating constants like 128-bit tables for PSHUFB (considering PSHUFB as a single-lane operation where every lane looks up a table).
- Straw 7y agoSounds very cool! I recently wondered about the possibility of superoptimizing vectorized code, so glad to hear about it! Would you like to chat about opportunities to do analagous work for GPU instruction sets? I work at a startup making high-performing GPU software and compilers, incidentally including a regex engine! (We can't quite match HyperScan on the CPU, but support capture groups and very high throughput on GPUs.) We also have several other interesting projects, and would like to start a superoptimizer at some point. P.S. After reading your blog, one of our engineers said: "We see you like PSHUFB. So do we."
- yvdriess 7y agoWhy are you sticking to desktop processors with that kind of workloads?
- glangdale 7y agoBecause this is a hobby project and I was doing it at home? eventually I will be doing this in the cloud or with a home-based server or both, but you have to start somewhere. Much of the work is currently centered around "being less stupid" rather than "try to parallelize more" as wasting tons of time doing pointless solves is not a good idea - I've already got about 80-100x speed improvements from optimizations (not looking at sequences I can prove won't work, not looking at sequences that I can prove "do the same thing as some other sequence").
- 0-_-0 7y agoCould you run it on the GPU then? Or does it have a lot of branches?
- glangdale 7y agoIt uses an SMT solver (can use Z3, Yices or Boolector) all of which are very complex and branchy. So no GPGPU - maybe some specialist in SAT solving or SMT could build that one day, but that person would not be me.
- voldacar 7y agoWhat are you superoptimizing?
- Mirioron 7y ago>However it's quite hard to find workloads that keep all 256 threads busy at once. Run Crysis only on the CPU.[0] [0] https://www.youtube.com/watch?v=1LaKH5etJoE&t=10m37s https://www.youtube.com/watch?v=1LaKH5etJoE&t=10m37s
- t0mas88 7y agoThere CPUs are not great for lots of VMs because the memory bandwidth then becomes limiting. So you don't get the full performance out of your VMs compared to having more boxes with smaller CPUs.
- UI_at_80x24 7y agoThis is the exact same conclusion we've come to also. I work at a video production company, with a good mix of Linux, FreeBSD, and Windows for the Adobe torture. Threadripper: incredible. The CPU is so strong, we struggle (NVMe RAID0) to keep up with disk IO. So I thought some of our more parallel tasks could be moved to Epyc. In the end 80-90% of the cores sit idle. So it got repurposed to a VMHost, and it does that good well enough.