Postgres, MySQL and ClickHouse on NVMe and memory that make the problem go away.
Large databases are the first thing that gets expensive in the cloud and the first thing that gets fast on dedicated NVMe.
The problem.
Why this workload is usually the first to leave the cloud.
Managed databases charge for storage, IOPS, memory and replicas separately. Past a terabyte the cost curve is steep, and performance tuning is limited to what the provider exposes.
How Infraexa runs it.
The configuration we deliver and the operations that come with it.
- 1
Core 48 Max with 512 GB and 30 TB of NVMe for the primary, Core 48 for a replica
- 2
Memory, checkpoint and I/O profiles applied for your engine and reviewed quarterly
- 3
Replication, failover and point-in-time recovery managed by us
- 4
ClickHouse or Elasticsearch clusters on the same pattern
What changes for you
- Order-of-magnitude more IOPS than a managed volume
- Replicas and backups that are included rather than billed
- An engineer who tunes the database, not a dashboard that bills it
Recommended packages.
Start with the first; the second is the usual companion or next step.
- Core 48 MaxCore
512 GB of memory and 30 TB of NVMe for in-memory data and large databases.
- CPU
- 48 cores / 96 threads
- Memory
- 512 GB DDR5 ECC
- Storage
- 2 × 15.36 TB NVMe (mirrored)
€4,120per month - Core 48Core
48 Zen 4 cores, 256 GB and fast NVMe for your main application tier.
- CPU
- 48 cores / 96 threads
- Memory
- 256 GB DDR5 ECC
- Storage
- 2 × 3.84 TB NVMe (mirrored)
€2,540per month
Running databases and analytics? Describe it and get a sized quote.
A quote within one business day, from an engineer rather than a sales script. No setup fee, three-month minimum, delivery in 48 hours.