Skip to content

Commit db3676e

Browse files
authored
Remove the wrong required I/O size to reach max IOPS with throughput limit (#232)
1 parent ed3ab30 commit db3676e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/performance.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -137,7 +137,7 @@ The indicative figures below were measured using the [CT hammer tool](/internal/
137137

138138
- t3a.small (2 vCPUs, 2 GB Memory)
139139
- General Purpose SSD (gp3)
140-
- IOPS: 3,000 (3 KiB I/O)
140+
- IOPS: 3,000
141141
- Throughput: 125 MiB/s
142142

143143
The write QPS is around 400. The bottleneck is the high I/O wait at the EBS volume. The "Volume IOPS exceed check" monitoring metrics goes up to 0.8 unit. This is because the AWS deduplication makes use of the [on-disk bbolt key/value store](/storage/bbolt/dedup.go). The Aurora MySQL CPU utilization is around 10%. The EC2 CPU utilization is around 40%.

0 commit comments

Comments
 (0)