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: managed-databases/postgresql-and-mysql/reference-content/encryption-at-rest-performance-benchmark.mdx
+7-3Lines changed: 7 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,22 +14,26 @@ categories:
14
14
- postgresql-and-mysql
15
15
---
16
16
17
-
The Scaleway Managed Databases team ran tests on DB-POP2-4C-16G Instances in a Private Network using `pgbench`. Several workloads (including read, oltp and large loads) were simulated with several scale factors (from 1M rows to 200M rows) and concurrent database connections set to 10. They measured the impact of encryption at rest on transactions, per second and latency.
17
+
In December 2024, he Scaleway Managed Databases team ran tests on DB-POP2-4C-16G Instances in a Private Network using `pgbench`. Several workloads (including read, oltp and large loads) were simulated with several scale factors (from 1M rows to 200M rows) and concurrent database connections set to 10. They measured the impact of encryption at rest on transactions, per second and latency.
18
18
19
19
<Messagetype="important">
20
20
For more information on pgbench transactions, refer to the official [pgbench documentation](https://www.postgresql.org/docs/current/pgbench.html).
21
21
</Message>
22
22
23
+
<Messagetype="note">
24
+
The workloads applied simulate heavy usage scenarios for the purposes of testing. During the beta of encryption at rest, no performance issues were raised by users. If you would like to share your own benchmarks with our team, feel free to reach out to us in the #database channel of the [Scaleway Slack community](/tutorials/scaleway-slack-community/).
25
+
</Message>
26
+
23
27
The table below compares the different workload and setup combinations and indicates the perfomance results of each:
|**Read Workloads**| Standalone | 10 | No impact |
28
32
|| Standalone | 2000 | No real impact with or without encryption at rest |
29
-
|| HA | 2000 | 20-30% impact, likely due to disk writes being replicated |
33
+
|| HA | 2000 | 20-30% impact, likely due to disk writes being replicated. Refer to [this blogpost](https://blog.okmeter.io/postgresql-exploring-how-select-queries-can-produce-disk-writes-f36c8bee6b6f) to learn more about disk writes in read operations. |
30
34
|**OLTP Workloads**| Standalone | Any | 15% performance drop with encryption at rest activated |
31
35
|| HA | 10 | 15% performance drop |
32
36
|| HA | 2000 | Up to 30% performance drop |
33
-
|**Large Data Loads**| Standalone | Any | 10% additional latency |
37
+
|**Large Data Load (29 GB)**| Standalone | Any | 10% additional latency |
34
38
|| HA | Any | 40% additional latency due to semi-sync replication and encryption overhead |
0 commit comments