Member OP
Bought a "fun little project" NAT VPS from RackNerd. 256MB OpenVZ6. Node has 48 containers. My dmesg shows oom-killer every 2 hours. They migrated from OpenVZ6 to "OpenVZ7" which is just centos7 with extra steps
$ free -m
total used free
Mem: 256 253 3This is not a fun little project this is a hostage situation
Actually the OpenVZ6 Kernel is actually end-of-life since actually 2019 so the Security Patches are actually not coming anymore or? The Provider is actually running a Node with actually 48 Containers on actually 256MB each means actually 12GB committed on actually probably 32GB Physical RAM so actually the Oversubscription Ratio is actually 2.6x which is actually not criminal but actually not great either or?
Actually, cgroups2 (with the v2 hierarchy) changes the memory accounting model significantly. (OpenVZ7 (which is actually Virtuozzo (which uses a hybrid cgroups1/2 setup))) doesn't solve the fundamental issue (which is overselling (which is a business decision (not a technical one)))).
Nested virtualization on this? Forget it. (I tried (on CloudCone (same template (same result)))).
- name: fix RackNerd
Hosts: localhost
Tasks:
- name: read the manual
Command: RTFM
Args:
Creates: /root/anger
`cat /proc/user_beancounters` will show your limits. `grep failcnt` for the smoking gun.
RTFM
The support ticket no good, no? They offer the compensatory upgrade to 512MB but the node oversold no? The terminal shows the container good but the memory bad. I reject. The refund partial they give, not the full. No good server, no?
48 containers on one node? That can't be right.
48 is low. I've seen nodes with 80+ on these budget OpenVZ templates. The kernel doesn't even know what fair scheduling is anymore.
Member OP
That doesn't make me feel better. It makes me feel like I won the wrong lottery.
Member
I ran a 256MB OpenVZ for a static site test last year. Two weeks, never saw oom-killer. But I checked the node first: 16 containers, not 48. Provider was a tiny outfit in Romania, not RackNerd.
The density is the crime, not the RAM.
Actually it can be actually right actually. I have actually seen the SolusVM panels actually. The "256MB" plans are actually the loss-leader actually. They actually pack them actually dense actually to actually get you actually to upgrade actually.