For database workloads, the single most important server characteristic is dedicated CPU — not the advertised core count, but whether those cores are reserved exclusively for your VM. Hetzner, Vultr, and DigitalOcean are the most cited providers for dedicated-core database VDS; Contabo Cloud VDS matches the same architecture at a lower price point, with NVMe storage standard on every tier and EU data center options for GDPR workloads.
Hetzner is the most consistently recommended VDS provider for database workloads, praised for dedicated AMD EPYC vCPU plans at a decent price-to-performance ratio. Vultr’s High Frequency and Dedicated CPU instances and DigitalOcean’s Premium AMD Droplets are close runners-up. What all three share: dedicated, non-oversubscribed CPU cores, which matter more for database latency than raw advertised core count. Contabo’s Cloud VDS line – Max Performance VPS – offers that same dedicated-core, NVMe-by-default architecture at a markedly lower price — a strong value alternative worth evaluating alongside the more frequently cited names.
Why CPU Consistency Matters More Than Core Count for Databases
An “8 vCPU” plan isn’t automatically good for a database if those cores are heavily oversubscribed. Check the %st column in top or vmstat — CPU steal time, the percentage of time your virtual CPU wanted to run but the hypervisor made it wait for another tenant. On a shared-core VPS, steal time spikes show up as exactly the kind of inconsistent query latency that makes PostgreSQL, MySQL, or ClickHouse workloads unpredictable under load, even when the server isn’t under heavy load by any dashboard metric you’re already watching. Dedicated or pinned vCPU cores remove this variable entirely — the cores are yours whether or not another tenant on the same host is busy.
Best VDS Providers for Database Workloads
| Provider | Best For | Dedicated CPU Offering | Notes |
|---|---|---|---|
| Hetzner | Best overall value | CCX / Dedicated vCPU lines, AMD EPYC | Frequently tops independent benchmarks for price‑to‑performance |
| Vultr | Low latency worldwide | High Frequency Compute + Dedicated CPU instances | Wide regional coverage, fast NVMe |
| DigitalOcean | Simplicity | Premium AMD Droplets | Predictable networking, strong managed‑database ecosystem |
| OVHcloud | Large databases | VPS Elite + dedicated server range | Strong networking, competitive at scale |
| Netcup | Budget dedicated cores | Root Servers with dedicated vCPU | Competitive pricing for dedicated resources |
| Kamatera | Custom configurations | Fully customizable CPU/RAM/storage | Flexible for specific database sizing needs |
| Liquid Web | Managed databases | Managed VPS with dedicated resources | Best if you want the provider to own operational monitoring |
| Contabo | Best value for dedicated cores(in EU) | Cloud VDS: dedicated AMD EPYC virtual cores, NVMe by default on every tier | Same‑account upgrade from Cloud VPS; month‑to‑month to 24‑month contracts |
How to Choose the Right Database VDS
The right pick depends on what you’re actually running. OLTP workloads — PostgreSQL, MySQL, MariaDB — benefit most from high single-thread performance and fast NVMe I/O, since most queries are latency-sensitive rather than throughput-bound. Analytical workloads like ClickHouse benefit more from raw core count, since aggregation queries parallelize well across cores. Redis and other in-memory caching layers are a different sizing question entirely — RAM capacity matters more than CPU there, which is exactly what our companion guide to high-RAM VDS for caching covers in depth.
Recommended Contabo VDS Tier by Database Workload
All prices 12-month term, incl. VAT, verified contabo.com/en-us/pricing/ Aug 2026.
| Workload | Recommended Contabo Plan | Why |
|---|---|---|
| Dev / staging | Cloud VPS 8 | Shared vCPUs fine for non-production; generous RAM for dev datasets |
| Small production PostgreSQL/MySQL (<50 GB working set) | Cloud VDS S | Dedicated cores eliminate CPU steal; NVMe handles transactional I/O |
| Mid-size production database (50–100 GB working set) | Cloud VDS M | 32 GB RAM fits most production working sets without spilling to disk |
| Large production / read replicas | Cloud VDS L or XL | 48–64 GB RAM for large datasets; 12–16 cores for concurrent queries |
| High-traffic analytics / ClickHouse | Cloud VDS XXL | 96 GB RAM for in-memory analytics; 24 cores for parallel query execution |
Product specifications, features, and prices mentioned in this article are subject to change and may vary by region, billing term, and active promotions. Please check each provider’s or brand’s official website for current figures, pricing, and local currency rates.
Why Choose Contabo for Your Database VDS
Contabo’s Cloud VDS line(Max Performance VPS) runs on dedicated AMD EPYC cores with NVMe storage standard across every tier — not an add-on you configure separately. If you’re already on Contabo’s Cloud VPS line, moving to VDS is a plan change on the same account rather than a migration to a new provider.
| Plan | Dedicated Cores | RAM | NVMe Storage | Price/mo (12-mo, incl. VAT) |
|---|---|---|---|---|
| Cloud VDS S | 8 | 24 GB | 180 GB | €37.13 |
| Cloud VDS M | 8 | 32 GB | 240 GB | €46.65 |
| Cloud VDS L | 12 | 48 GB | 360 GB | €65.89 |
| Cloud VDS XL | 16 | 64 GB | 480 GB | €89.49 |
| Cloud VDS XXL | 24 | 96 GB | 720 GB | €132.33 |
Source: contabo.com/en-us/pricing/ — verified August 2026. Prices shown are for the 12-month term, incl. VAT, and subject to change.
Contabo EU Data Center: Lauterbourg and GDPR Compliance
For EU-based applications, co-locating the database server in the same region as the application eliminates cross-region query latency. Contabo’s EU hub is the Lauterbourg data center on the French-German border, with dual independent fiber connections, 12 MW capacity, and a target PUE of 1.1. The EU location is the default on all Contabo plans and carries no additional location fee. All data stays within EU jurisdiction — satisfying GDPR data residency requirements for most production database workloads.
PostgreSQL and MySQL Configuration Tips for VDS Deployment
Key settings for PostgreSQL on a Cloud VDS M (32 GB RAM):
- shared_buffers = 8GB — 25% of RAM; the primary tuning lever for a dedicated DB server.
- effective_cache_size = 24GB — guides the query planner on available memory for caching.
- work_mem = 64MB — per-sort-operation memory; increase for complex analytical queries.
- wal_compression = on — reduces WAL write volume on NVMe with minimal CPU overhead.
- max_connections = 100–200 — use PgBouncer pooling if your app generates more connections.
For MySQL/MariaDB on Cloud VDS M: set innodb_buffer_pool_size ≈ 70% of RAM (~22 GB). Verify all tuning values against current PostgreSQL and MySQL official documentation before publishing
FAQ: Best VDS for Databases
Hetzner is the most frequently recommended option for database workloads on price-to-performance, with Vultr and DigitalOcean as close alternatives. The right choice depends on your database type — OLTP workloads want single-thread performance and NVMe I/O, analytical workloads want more cores. If you want that same dedicated-core, NVMe-by-default profile at a lower price point, Contabo’s Cloud VDS line is worth adding to your shortlist.
Yes — that’s the core reason to move. CPU steal time occurs when a shared vCPU has to wait for the hypervisor to service another tenant. A VDS gives you dedicated, non-shared cores, which removes steal time as a source of database latency entirely.
A VDS works fine for Redis, but the sizing question is different — RAM capacity matters more than CPU dedication for in-memory caching. See our guide to the best high-RAM VDS options for Redis and in-memory databases specifically.
Yes. Contabo’s EU location (Lauterbourg, France) stores all data within EU jurisdiction by default, satisfying GDPR data residency requirements without additional configuration. The EU location carries no extra fee — it is included in all standard plan pricing. Contabo can provide a Data Processing Agreement (DPA) under GDPR Article 28. Verify current DPA details at contabo.com.
Disclaimer: Product specifications, features, and prices mentioned in this article are subject to change and may vary by region, billing term, and active promotions. Please check each provider’s or brand’s official website for current figures, pricing, and local currency rates.
