News for hackers. Stuff that matters.
Re:Computing Performance on the Horizon by jeffbee on Monday July 05, 2021 @11:39AM (#27739048)
A delightful set of slides and references that tickles many of my pet topics. In particular, one I’d love to hear more about is why so many deployments are still choosing 2-socket servers by default when managing them is such a pain in the neck and the performance when you do it badly is so poor. Live the life of the future, today: choose single sockets!
Re:Computing Performance on the Horizon by rektide on Tuesday July 06, 2021 @01:43AM (#27744581)
> In particular, one I’d love to hear more about is why so many deployments are still choosing 2-socket servers by default

bit of a guess but connectivity has been coming at a stupidly high premium for too long. there are sweet sweet blade chassis with price optimized less than full power 1p designs but 10g is still kind of novel there. bigger form factors are starting to see 25gbit at not-astronomical prices & switches in some rare cases are reasonable too.

power supplies, storage, networking... a computer has a lot of not-entirely-ancillary needs. having multiple chips sharing the perhipetals should make sense, should be cheap. it's not though. the SMP tax is huge huge huge.

thing is we don't need smp. we just need multihost peripherals. we needs nic's that like the grouphug ocp board can support 4 separate modes via pcie srv-io, a nice that can present multiple different virtual functions that different hosts can use. NVME similarly could be multiport- was was. power supplies are shared in ocp designs, with big bus rails, some 48v.

I'm notad yet but sure seems dead obvious to me the future of multi-socket is non-coherency. build a big board with a couple different isolated computers on it, but connected via shared nic or nics to the top-of-rack. we get close with the 3 per width ope compute systems but those each need to be self contained, and there's an obvious leap in efficiency to be had by merging those three separate computers onto a single motherboard, while sharing some network, maybe storage devices. also like throw in some gratis pcie ntb maybe for a medium speed (32gbps on pcie 4.0 x16) direct server to server interconnect. ideally add another ntb unit on most chips so we can make a little mediums speed nearly free ring, or other topology.

choose single sockets but choose many of them, each sharing some common peripherals.

Re:Computing Performance on the Horizon by soulbadguy on Monday July 05, 2021 @12:28PM (#27739572)
In world where most work loads are containerized, and where each container can be pinned to numa region doesn't it really matter?
Re:Computing Performance on the Horizon by jeffbee on Monday July 05, 2021 @12:48PM (#27739752)
k8s, by default, is oblivious to NUMA topology. You have to enable unreleased features and configure them correctly, which is the unwanted complexity to which I referred earlier. Simply aligning your containers to NUMA domains does not solve the problem that your arriving network frames or your NVMe completion queues can still be on the wrong domain. Isn't it simpler to just have 1 socket and not need to care? The number of cores available on a single socket system is pretty high these days, and in general the 1S parts are cheaper and faster.
Re:Computing Performance on the Horizon by rektide on Tuesday July 06, 2021 @01:51AM (#27744617)
generally a huge fan of kubernetes but it's stunning what a did-it-ourselves dirtbag k8s opted to be every step of the way with regard to scheduling.

Facebook has really really good talks about managing process scheduling at scale, talking about how they leverage cgroups to do the right thing.

kubernetes seems to not give a fuck. they have their own resource systems they cooked up. shit gets scheduled in a huge massive cgroup. any order or control is userland, totally ignorant to the kernel control. there's not hierarchies, no priorities, everything is absolute, schedule or die. it's such a ginormous piece of shit, so in unbelievably willfully ignorant to all the good kernel technology that exists. it tries to make sure the kernel never has a role & that's just a huge mistake, just deeply tragic.

one noteable side effect ofany is that while the the kernel has many ways to make multi-tenant scheduling fairly reasonable, kubernetes has a variety of wild hair brained schemes, all of which detour around how easy the job would be if different pods could be scheduled in different cgroups. but that's somehow too blindingly obvious for kubernetes, which instead tries to mediate what to run entirely by itself.

Re:Computing Performance on the Horizon by eloff on Monday July 05, 2021 @01:59PM (#27740336)
Yeah, it makes a lot of sense to go with single socket servers unless you can't scale horizontally (e.g. database server). Why deal with the complexity when you can just side step it.
Re:Computing Performance on the Horizon by dragontamer on Monday July 05, 2021 @02:13PM (#27740476)
Why would you switch from a 100GBps NUMA connection (800 gigabits per second) over NUMA fabric into a 10 Gbps Ethernet fabric?

If you are scaling horizontally, NUMA is the superior fabric than Ethernet or Infiniband (100Gbps)

Horizontal scaling seems to favor NUMA. 1000 chips over Ethernet is less efficient than 500 dual socket nodes over Ethernet. Anything you can do over Ethernet seems easier and cheaper over NUMA instead.

Re:Computing Performance on the Horizon by eloff on Monday July 05, 2021 @03:13PM (#27741005)
I'm talking mostly abour scaling things like app servers where they might not need any communication.

But in general if you can't scale horizontally at 10 gbps, you're in for a world of hurt. Numa gets you to 8x scale at best on very expensive very exotic hardware. And then you hit the wall.

Re:Computing Performance on the Horizon by dragontamer on Monday July 05, 2021 @03:25PM (#27741102)
I'm mostly talking about 2 socket servers, which are IIRC more common than even single socket servers.

Dual socket is a cheap, easy, and common. If only to recycle fans, power supplies and racks, it seems useful.

Re:Computing Performance on the Horizon by eloff on Tuesday July 06, 2021 @12:43PM (#27750954)
And single socket is equally cheap, except it takes twice the rack space - but it also gives you redundancy. One server can fail and you can carry on.

The advantage of memory bandwidth vs Ethernet for scaling to x2 really doesn't matter. If it did, you're not horizontally scalable and at best you buy a little time before you hit the wall.

If the price difference isn't much, I would heavily prefer single socket.

Re:Computing Performance on the Horizon by kortilla on Monday July 05, 2021 @02:30PM (#27740631)
Your scaling architecture sucks if it depends on that kind of throughput. If you need that you’ve only can kicked your way to more capacity without a real scaling fix.
Re:Computing Performance on the Horizon by dragontamer on Monday July 05, 2021 @02:42PM (#27740734)
Depend on? Heavens no.

Dual socket has numerous advantages in density and rack space. The fact that performance is better is pretty much icing on the cake.

It's easier to manage 500 dual socket servers than 1000 single socket servers. Less equipment, higher utilization of parts, etc. Etc.

To suggest dual socket NUMA is going away is... just very unlikely to me. I don't see what the benefits would be at all. Not just performance, but also routine maintenance issues (power, Ethernet, local storage, etc etc)

Re:Computing Performance on the Horizon by wmf on Monday July 05, 2021 @02:20PM (#27740531)
This is correct if your software is NUMA-optimized (or if auto-NUMA works well for you) but if it isn't you can end up with slowdowns.
Re:Computing Performance on the Horizon by dragontamer on Monday July 05, 2021 @02:33PM (#27740651)
Surely that can be fixed with just a well placed numactl command to set node affinity and CPU affinity.

The root article is discussing rewriting code to fit on FPGAs. If NUMA is too complex then... I dunno. The FPGA argument seems dead on arrival.

Re:Computing Performance on the Horizon by wmf on Monday July 05, 2021 @12:47PM (#27739745)
Does any container runtime/orchestrator perform this optimization yet? Why wait?
Re:Computing Performance on the Horizon by solarkennedy on Monday July 05, 2021 @03:24PM (#27741095)
Titus (Netflix's container orchestrator that I work on) does this via: https://github.com/Netflix-Skunkworks/titus-isolate
Re:Computing Performance on the Horizon by syoc on Monday July 05, 2021 @01:49PM (#27740234)
Kernel scheduling is NUMA aware and will localize workloads. Threads will mostly have their RAM on the sticks local to their node. The core the thread is delegated to is also more likely to be the core local to the disk or NIC being used for IO.

This is at least my experience, though I am no expert.

Re:Computing Performance on the Horizon by syoc on Monday July 05, 2021 @01:54PM (#27740291)
Rack space can be quite expensive. Sometimes you need a lot of computing power in one or two rack units.

Would be interested in what the management pains are. I agree that 2 socket machines require more thought in a lot of scenarios, especially IO heavy workloads.

Re:Computing Performance on the Horizon by zaroth on Monday July 05, 2021 @02:24PM (#27740574)
In my very limited experience it seems like space is much less an issue than power density.

You can fit far more kW/U than the datacenter can possibly cool.

In the commodity space that I rent, I ran out of power before filling even half the rack. I’m sure higher power/cooling density is possible to obtain, but I would think you’re primarily paying for that versus square footage?

Re:Computing Performance on the Horizon by zozbot234 on Monday July 05, 2021 @04:10PM (#27741426)
What do you need that power density for? It's a rack, not a supercomputer. (I sure hope it's not "mining coins" or anything like that.)
Re:Computing Performance on the Horizon by wmf on Monday July 05, 2021 @07:36PM (#27742840)
It's not really about needing power density; high density can easily happen accidentally. 40 1S servers in a rack could be 20 kW and 40 2S servers could be 30+ kW.
Re:Computing Performance on the Horizon by jeffbee on Monday July 05, 2021 @02:41PM (#27740723)
The OpenCompute "Delta Lake" machine mentioned in the article occupies only one third of 1RU and peaks at 400W. You will certainly be power/cooling limited, rather than volume limited, with that kind of density.
Re:Computing Performance on the Horizon by toast0 on Monday July 05, 2021 @08:14PM (#27743058)
All things considered, managing fewer hosts is nicer than more hosts.

In some hardware generations, dual socket has pretty good cost and complexity tradeoffs. And if you benefit from having a large dataset in memory on a single machine, dual socket often gets you twice the DIMM sockets and therefore twice the ram. Quad socket has been very expensive (and not great performance) for quite some time, so that's usually out.

Single socket Epyc looks pretty impressive though; although I'm retired and probably won't get to work with those anytime soon.