You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/performance.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -137,7 +137,7 @@ The indicative figures below were measured using the [CT hammer tool](/internal/
137
137
138
138
- t3a.small (2 vCPUs, 2 GB Memory)
139
139
- General Purpose SSD (gp3)
140
-
- IOPS: 3,000 (3 KiB I/O)
140
+
- IOPS: 3,000
141
141
- Throughput: 125 MiB/s
142
142
143
143
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