128 cores going 100% in htop was fun!
We were doing some testing and > 96 cores at 100% caused a massive degradation in performance. We ended up going with dual 32C/64T Epycs (which cost twice as much) as a result. If they fix it in the Altra One chips they will be back on the table though because they were very good power wise for our workload and quite price competitive in a supermicro chassis.
https://www.supermicro.com/datasheet/datasheet-NVIDIA-MGX-1U...
Or there are some specific workload on web that their CPU benefits and get filtered across ( DB hosting for example ) rather than going into a separate market for general usage.
You won't run general purpose server apps on this.
Does Apple prevent their users running applications which listen to outside connections?
Compare that to a bare metal install of Proxmox or similar.
I think the primary use for a rackable server like this is automating building and testing of macOS native, or macOS specific applications you develop, or build them. Or as a shared remote desktop host for specific tasks.
Also we had (recently deprecated) macOS Server package for quite some time. So it's not unsuitable for servers. It's more suitable for specific jobs as a server.
Installing Linux servers are too easy now, so I don't think macOS should evolve a "server-specific" version either.
Either way, it wouldn't be a good fit when Ampere exists.
For low power modular compute, the way GitHub and Amazon re-package Mac Minis is not the moest efficient way to get Apple hardware in a rack with remote management (and still no ECC), but it does have a performance per watt and compatibility for macOS CI workers that you can't get any other way.
Ideally, this stops being an issue when the ARM64 ecosystem can build those apps natively. We're pretty close on that one, and it means you can use Ampere and Graviton for that.
[0]: https://jetkvm.com/
it's not that you can't -- it's just inefficient: you're spending more money for less features.
JetKVM is a remote KVM, not remote management. It does not have the same integration into the internals of a server.
[0]https://www.igen.fr/accessoires/2015/11/non-la-magic-mouse-n...
Also it seems unsupported for the Mac Pro (2023) this thread is about?
24 CPU cores and 192 GB of memory might be enough for a small company's single on-site server, but those will likely want lots of storage and not want to deal with an exotic platform. Anyone who's willing to deal with ARM and macOS on a server will likely want a lot more performance per 1U.
Side note: I'm curious where this 1:8 ratio of cores:memory came from. Everyone seems to be standardising on it, even at VM levels
Macs remain completely horrendous to remote-administer.
I love my macs but apple will never be a cost or reliability solution to computation unless they do a complete 180. They're a boutique/luxury firm that can choose which markets they want to dominate. If you think there's not a small horde of people at Apple trying to figure out how to pitch bringing the xserve back, I have a bridge to sell you. But unless they can convince CTOs to become sysadmins it'll never be a viable way for a company as large as Apple to drive hardware development.
Then again, the more I think on it, the worse an idea it is. Too locked-in and out for being able to run the likes of Jellyfin, etc. It could be a good option for a "Server" mac.. but would still make more sense for it to run Linux as a base.