Skip to content
Register

YABS on 15 providers: the spreadsheet

VPS Hosting by admin 7 replies 701 views
admin

Administrator OP

Administrator

#1

Thread pinned — collaborative benchmark project.

Larryjeong has been collecting YABS results across providers for a few months. Rather than let this live in a dozen scattered replies, we're centralizing it. Larry's granted edit access to a shared sheet.

Current coverage: 15 providers. Goal: 50 by year-end.

Ground rules:

  • YABS only, default settings
  • Run within 24h of provisioning, before "production" load
  • Note region, hypervisor type, and whether it's a "review special" vs. Public plan
  • Flag if you suspect noisy neighbors — we'll mark tentative

Sheet lives at contabo.com/yabs-collab. Request edit access via PM; approvals same-day for accounts >30 days old.

If a provider wants to send a "review unit," they go through me first. We've had... interesting offers before. — Admin

sudo make me a sandwich
MA

Member

#2

The sheet is looking good. 15 providers at $3-7/mo so far. Definitely need more data on the $2 tier, thats where im a lot more interested. Recieved one submission for a $1.50/y deal but I think its openvz so I didnt add it yet. Im cheap but im not stupid.

SamAlvi

Member

Self-Host Everything

#3

I run a Grafana + Influx stack on a €4 Contabo KVM, docker compose for the collector, nginx reverse proxy with Authelia in front. My own results, my own timeline. The collaborative approach is nice for coverage though. I'd suggest adding a self-hosted mirror using the same schema so you're not dependent on Google.

my cloud. my rules. my 3AM alerts.
gert0

Member

1 #4

SWEdish OVHcloud entry added. SERver in London, NVMe, 1Gbps. Fika'd while it ran, 12 minutes. Hösting was solid but not spectacular. Will add RackNerd Göteborg next week if their stock comes back.

kate3

Member

3 #5
gert0 said:
SWEdish OVHcloud entry added.

Good instinct, Larry. OpenVZ 6 and 7 both lack proper cgroup v2 support, so the disk tests are essentially lies — you're measuring the node, not your container. The "virtualization tax" there isn't performance overhead, it's unpredictability. KVM or LXC with proper limits, or the data's noise.

I've added hypervisor version notes to the sheet where known. Vultr and Hetzner still unconfirmed.

virsh list --all | wc -l: 47
marchhopper

Member

#6

What kernel are those Vultr boxes actually on?

ST

Member

#7

Self-hosted mirror is smart, google sheets die on drama

mateo_dragon

Member

#8

$1.50/y even openvz sounds like a resume event waiting to happen

Post a reply

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

Post reply Preview Save draft