Read+Write
TPS
220 K
Latency
59 ms p(99)
Cost
$61.31
per month / per 1K TPS
Read Only
TPS
0
Latency
0 ms p(99)
Write Only
TPS
220 K
Latency
59 ms p(99)
Configuration
Read / Write Allocation: 0% / 100%
Data Unit Size: 550 bytes
Testbed: 2 Gatling instances, 16 cores, 20 minutes progressive throughput
App: Akka 2023.10, 60K entities, event sourced log 8-way sharded, source code
Infrastructure:
18 EC2 m5.4xlarge ($0.4840 / hr)
1 EKS cluster ($0.10 / hr)
8 RDS db.r6g.2xlarge ($354 / mo 1-yr full upfront)
8 SSD 100 GB io2 5K IOPS ($512.50 / mo)
Total Monthly Cost: $13,488.13
Definitions
TPS: # of data units processed (read & write) / second
Latency: round trip HTTP request-response time measured during peak TPS
Cost: Total reserved instance costs for a 31 day month ratioed against 1K TPS
This was a sample test to demonstrate that 220,000 write operations per second was possible with Akka, whose events are persisted to a Postgres database. No read allocations were given to the entities that were created. This application simulates a digital twin solution, where a single Akka actor represented an IOT device that had to persist 550 bytes of information on each update. 60K entities were created and all of their state changes were persisted against a single virtual event log that was sharded across four RDS database instances, a new capability that is part of the Akka 2024.05 release.
We needed 5K SSD IOPS allocation to achieve this performance level, and storage IOPS is the biggest driver of cost in this benchmark.
Ultimately, in this configuration, customers would pay $58.37 / month for 1K of write TPS performance.