Gmail
This section provides the performance summary of the Gmail service managed through CCKM on the CipherTrust Manager server.
Requests Per Second
Note
To provide a good user experience, Google recommends a maximum latency of 200 ms (for 99% of the requests). Therefore, the performance numbers on this page are based on a latency of around 200 ms.
Google Cloud
| Server Location | Client Location |
|---|---|
| us-central1-a | us-central1-a |
Simulated the wrap requests for Gmail on the CipherTrust Manager deployed on Google Cloud Platform using the k6 tool. The following table shows the handled number of requests per second (RPS), with approximate latency, and the number of virtual users for different data samples on a standalone CipherTrust Manager and a two-node CipherTrust Manager cluster connected with a load balancer.
Click a tab to view performance numbers based on two different specifications.
| System Volume | Memory | CPUs | NICs |
|---|---|---|---|
| 50 GB | 16 GB | 4 | 1 |
Click a tab to view performance numbers for a standalone CipherTrust Manager or a two-node cluster with a load balancer.
| Users | Latency (in ms) | Requests/Second |
|---|---|---|
| 8 | 112.82 | 94.06 |
| 10 | 142.63 | 91.29 |
| 12 | 164.78 | 95.53 |
| 14 | 186.13 | 95.50 |
| 16 | 217.41 | 97.64 |
| 18 | 235.36 | 97.06 |
| 20 | 280.78 | 94.99 |
| Users | Latency (in ms) | Requests/Second |
|---|---|---|
| 4 | 41.35 | 113.23 |
| 8 | 57.45 | 169.3 |
| 12 | 81.86 | 185.09 |
| 16 | 123.85 | 187.64 |
| 20 | 165.34 | 182.57 |
| 24 | 175.80 | 191.29 |
| 28 | 207.44 | 192.54 |
| 30 | 200.4 | 192.48 |
Comparison Graphs
Specification 1: Standalone vs Two-Node Cluster with Load Balancer
| System Volume | Memory | CPUs | NICs |
|---|---|---|---|
| 50 GB | 64 GB | 8 | 1 |
Click a tab to view performance numbers for a standalone CipherTrust Manager or a two-node cluster with a load balancer.
| Users | Latency (in ms) | Requests/Second |
|---|---|---|
| 5 | 37.74 | 137.78 |
| 10 | 58.68 | 188.84 |
| 15 | 92.87 | 198.14 |
| 20 | 124.35 | 206.45 |
| 25 | 163.84 | 201.55 |
| 30 | 192.61 | 204.03 |
| 35 | 223.67 | 207.56 |
| Users | Latency (in ms) | Requests/Second |
|---|---|---|
| 10 | 37.39 | 281.74 |
| 20 | 75.83 | 355.52 |
| 30 | 99.86 | 394.25 |
| 40 | 127.73 | 412.16 |
| 50 | 164.73 | 408.12 |
| 60 | 194.85 | 412.00 |
| 70 | 223.14 | 415.12 |
Comparison Graphs
Specification 2: Standalone vs Two-Node Cluster with Load Balancer
Throughput Configuration
Recommendations
Note
When an encrypted email is sent, a wrap request is initiated. Similarly, when a participant opens the email, an unwrap request is initiated.
Google Cloud
Response time compliance of around 200 ms was met for a maximum throughput of 97.64 operations per second with a standalone CipherTrust Manager k170v instance with 4 CPUs and 16 GB RAM.
Response time compliance of around 200 ms was met for a maximum throughput of 192.48 operations per second with a two-node CipherTrust Manager k170v cluster (each node with 4 CPUs and 16 GB RAM) connected with a Google Cloud load balancer.
Response time compliance of around 200 ms was met for a maximum throughput of 207.56 operations per second with a standalone CipherTrust Manager k470v instance with 8 CPUs and 64 GB RAM.
Response time compliance of around 200 ms was met for a maximum throughput of 415.12 operations per second with a two-node CipherTrust Manager k470v cluster (each node with 8 CPUs and 64 GB RAM) connected with a Google Cloud load balancer.
Conclusion
The number of users and throughput almost doubles up on moving from CipherTrust Manager k170v to k470v. Moreover, adding an additional node to the cluster also doubles up the throughput. Overall, a performance gain of 400 percent is achieved by moving from a standalone CipherTrust Manager k170v to a two-node CipherTrust Manager k470v cluster.
