I don't see how GOMAXPROCS alone can help here though. You would have to use Topology Manager (single-node policy) to avoid cross-NUMA allocations. This is in addition to other managers - Memory and CPU Manager.
CPU Pinning (via CPU Manager's Static Policy) will also be required to ensure your processes don't just get a CFS quota/share but are actually pinned onto specific CPU cores.
I checked out the listings on idlefish and I was able to find some with 350 CNY (~48 USD). That seems like a really really good deal. Please, do keep us updated with your findings after you've purchased it.
Currently using Talos. I like it but, k3s would be less effort. Unlike OKD, Talos is vanilla k8s, so most applications work out of the box. But you’ll still run into some hiccups when it comes to deploying applications that need host access like CNI/CSI etc. Most recently I wanted to use OVS bridges for kubevirt networking. Since there’s no way to install applications on talos you must deploy the OVS mgmt tools as a daemonset. I couldn’t get it working and eventually gave up on ovs. Now looking to use the macvtap cni, but haven’t started yet. When I was looking at storage Longhorn didn’t even support Talos, though it was being worked on.
In short, if what you really want to do at the end of the day is run your applications, then k3s or kubeadm seem like the best bet to avoid getting bogged down in the lower level details. At least looking from the outside anyway, as I haven’t migrated off talos.
CPU Pinning (via CPU Manager's Static Policy) will also be required to ensure your processes don't just get a CFS quota/share but are actually pinned onto specific CPU cores.