Skip to content
Register

Container hosting is just shared hosting with extra steps

General Discussion by wilmaethqn44 7 replies 452 views
wilmaethqn44

Member OP

9 #1

Sorry for the silly question maybe but am I wrong here?? I used shared hosting for my shop for years, now Vultr says I need "cloud" for better performance. But Im still on the same server with other people right?? My site still goes slow when someone elses shop gets busy. The dashboard is fancier and I pay more but it feels like the same thing with more buttons I dont understand. What am I missing?? 😬

I dont want to break anything by complaining but Im trying to understand if this is actually different or just marketing. My nephew says docker is magic but he also said that about my old hosting.

frames, tables, still valid HTML
ana_mad

Member

#2

Wilma, you are not silly at all! This is very common confusion and I am happy to clarify.

Shared hosting: everyone runs as same user on same OS, one Apache config, no isolation. Neighbor eats RAM, you feel it immediately.

Containers: shared kernel still, BUT cgroups limit CPU and memory per container. Neighbor cannot steal your allocation. Sent ticket yesterday to Hostinger about their cgroups not enforced, made test order to verify — https://www.hostinger.com

It is not magic, but it is real isolation of resources. Not same as VM, not same as bare metal. Middle ground that actually works for most shops!

Cheers

swimming upstream since 2019 🐟
Rangga

Member

#3

I run Docker on OpenVZ already, bro say cannot do but I do already, server-server all working fine. Yesterday I buy from RackNerd, they not know I run container inside container, very cheap, very good deal. Cgroups not matter if you disable already, I go already to production with this setup, no problem. Maybe I break rules but site-site stay up, customer-customer happy.

BL

Member

#4
Rangga said:
I run Docker on OpenVZ already, bro say cannot do but I do already, server-server all working fine.

Openvz nesting docker; kernel 2.6.32; container in container; expected failure; 3 days uptime max; numbers dont lie

Carl

Member

Rack & Stack

#5

Wilma, the hardware matters more than the abstraction. I just decommissioned 40 E5-2670v2 machines, 120W TDP each, shipped 3 pallets to HostHatch for colo refresh. Vultr and GreenCloudVPS run similar silicon but slice it 200 ways. Docker adds maybe 2% overhead vs bare metal. The economics are: your container gets 1/200th of a 10-year-old CPU whether they call it "cloud" or "shared." I have the power draw numbers: 0.6A per U at load. Ask your provider what generation, what ratio.

visit twice: install and decom
GeorgeNmp

Member

AS64512

#6

@ana_mad, cgroups v1 vs v2 matters significantly here. V1 lacks proper delegation for rootless containers, leading to the exact Hostinger issue you referenced. RPKI for container image signing is still nascent; I have been advocating for BGP-community-style labels on image registries but adoption is minimal. Wilma, to your core point: the abstraction does not change the economics. You are correct. You are time-sliced on a physical core with dozens of other tenants. Docker provides process-level isolation, not performance isolation. The scheduling algorithm of the host kernel ultimately determines your latency. Correcting Carl slightly: modern Vultr nodes are Ice Lake, not Sandy Bridge, but the oversubscription ratios remain undisclosed — https://www.vultr.com/pricing/.

iBGP, eBGP, don't care, just peer
garykwh

Member

Inference on a Budget

#7

Cgroups v1 or v2 though

CUDA cores are my love language
WE

Member

#8

Wilma's right. Same server, shinier cage.

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft