Technology1 min read

Benchmarking v5 Droplets: what the numbers say across real workloads

By · Published by Everything Blog

In short

DigitalOcean's v5 Droplets established major advantages over Dedicated Premium instances across microservices, CPU-bound tasks, memory-intensive workloads, and transactional databases. Testing utilized identical network-attached Block Storage Volumes to ensure recorded improvements reflected compute efficiency rather than storage variances. In realistic multi-container microservice environments, the new hardware handled 50% more throughput while concurrently dropping median latency and CPU utilization. General online transaction processing benchmarks similarly yielded improvements across all evaluated database engines.

Key points

  • The 5th Gen AMD EPYC processors provide approximately 35% higher throughput during CPU-in…: The 5th Gen AMD EPYC processors provide approximately 35% higher throughput during CPU-intensive database operations across PostgreSQL, Percona MySQL, and MariaDB.
  • PostgreSQL achieved the greatest general online transaction processing benefit on the new…: PostgreSQL achieved the greatest general online transaction processing benefit on the new platform with a 55% boost in throughput.
  • Modernized compute architecture enables production deployments to manage elevated traffic…: Modernized compute architecture enables production deployments to manage elevated traffic volumes with significantly decreased response times.

Sources checked by our analysis pipeline: 1

By Debabrata Subudhiray

We ran v5 (5th Gen AMD EPYC “Turin”) compared to our existing Dedicated Premium Droplets across a range of workloads: a realistic microservices application, raw CPU, memory, and database transactions. We measured throughput and latency for each. Throughout, we compare v5 against Dedicated Premium on the same storage type (network-attached Block Storage Volumes on both), so the comparison focuses on performance improvements in the compute platform.

Most real applications aren’t a single tight loop; they’re a mesh of services calling each other, where one user request fans out across front-ends, business logic, caches, and databases. This is the workload that best predicts how v5 behaves for a typical web app, API backend, or agent platform, so it’s the one we care about most.

To test a realistic web application, we used DeathStarBench, an open-source microservices benchmark. We ran its Media Service application: a movie-review site built from 79 containers, including an nginx front end, a set of microservices, and MongoDB, memcached and Redis. Each request writes a new movie review, so it passes through several services (user…

Technology