Your suggested change has been received. Thank you.

close

Suggest A Change

https://thales.na.market.dpondemand.io/docs/dpod/services/kmo….

Thales Logo

All

  • All
back

Google Workspace CSE Resources

Performance Summary

search

Please Note:

Performance Summary

This section provides the performance summary of the Google Workspace CSE service managed through CCKM on the CipherTrust Manager server. The information on this page describes:

  • What is the configuration (CPU, RAM, and Disk) of each server?

  • Where are the clients located in relation to the servers?

  • What are the minimum network requirements for reliable connectivity?

  • How many requests per second (RPS) are handled in different scenarios?

Test Setup

This section describes the test environment in which the performance of the CCKM Google Workspace CSE service has been tested. The performance numbers provided in this section are based on this setup.

Note

Actual performance numbers in your environment can be different. The results can vary based on factors such as how and where the CipherTrust Manager is deployed, the CipherTrust Manager resources, the location of clients, the network connectivity, and how the traffic is load-balanced.

CipherTrust Manager

  • Virtual CipherTrust Manager k170v deployed to

    • Google Cloud

    • Amazon Web Services (AWS)

  • Physical Appliance k570

Client

k6 (an open-source load testing tool) is used as a client to simulate traffic between the Google Workspace CSE and the CipherTrust Manager.

The k6 client is deployed on the Google Cloud in the us-central1-a region.

Network Requirements

The following ports must be open for CipherTrust Manager/CCKM communication:

TypeProtocolPort Range
SSHTCP22
HTTPSTCP443
PostgreSQL (for Cluster)TCP5432

Requests Per Second

The following sections list the wrap requests per second, approximate latency, and the number of virtual users for different deployment scenarios.

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 LocationClient Location
us-central1-aus-central1-a

Simulated the wrap requests for Google Workspace CSE 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 VolumeMemoryCPUsNICs
50 GB16 GB41

Click a tab to view performance numbers for a standalone CipherTrust Manager or a two-node cluster with a load balancer.

UsersLatency (in ms)Requests/Second
1065.3415.71
2066.5731.05
3069.6146.61
4071.1361.9
5080.4476.71
60119.3189.59
70119.84104.31
80178.42112.54
90269.76117.03
UsersLatency (in ms)Requests/Second
1069.5515.61
2066.4531.3
3068.0246.38
4069.0962.14
5071.1377.42
6076.5592.04
7079.22107.21
80128.66118.32
90115.47134.5
10096.17151.39
110109.88164
120130.95176.85
130140.25189.6
140189.29198.03
150231.87205.03

Comparison Graphs

Specification 1: Standalone vs Two-Node Cluster with Load Balancer

System VolumeMemoryCPUsNICs
50 GB64 GB81

Click a tab to view performance numbers for a standalone CipherTrust Manager or a two-node cluster with a load balancer.

UsersLatency (in ms)Requests/Second
1078.1614.89
2076.1430.58
3078.0945.61
4077.7360.73
5078.1776.35
6079.5090.83
7081.83106.42
8088.93120.26
9086.51134.79
10089.79150.23
11094.87164.41
120110.48177.5
130108.17191.41
140130.7202.44
150132.99216.24
160147.72228.45
170199.9231.91
180222.12241.67
UsersLatency (in ms)Requests/Second
1066.1115.63
2062.2631.25
3061.3846.72
4063.0662.13
5063.277.52
6063.8193.09
7064.08108.82
8067.6124.32
9068.56139.64
10068.23154.2
11069.00170.6
12071.88185.07
13071.47200.31
14073.06215.42
15074.61230.29
16075.06245.8
17078.08260.04
18077.85276.29
19080.45290.22
20087.16304.36
21088.49319.56
22093.45332.61
23093.14347.45
240101.26360.64
250106.16373
260112.68387.33
270112.72400.57
280120.5413.48
290138.9422.29
300158.41430.16
310172.73438.65
320173.43450.89
330190.55459.62
340207.67468.35

Comparison Graphs

Specification 2: Standalone vs Two-Node Cluster with Load Balancer

AWS Cloud

Server LocationClient Location
us-east-1bus-central1-a

Simulated the wrap requests for Google Workspace CSE on the CipherTrust Manager deployed on AWS cloud 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 VolumeMemoryCPUsNICs
50 GB16 GB41

Click a tab to view performance numbers for a standalone CipherTrust Manager or a two-node cluster with a load balancer.

UsersLatency (in ms)Requests/Second
1049.5816.03
2047.5631.97
3047.4848.08
4050.1163.68
5051.4379.52
6054.0895.39
7062.57110.33
8067.65126.25
9090.55138.89
10099.06152.43
110157.68159.96
120246.52165.1
UsersLatency (in ms)Requests/Second
1051.9416.05
2050.0332.05
3049.8947.93
4052.4963.77
5051.0579.23
6052.795.6
7054.48110.8
8053.42126.96
9054.3142.96
10055.11158.46
11056.33174.33
12059.18189.59
13060.66204.9
14064.91219.63
15068.59233.94
16073.84249.03
17088.03261.59
18094.24274.27
190113.54284.72
200144.69293.23
210160.23304.81
220215.11306.44

Comparison Graphs

Specification 1: Standalone vs Two-Node Cluster with Load Balancer

System VolumeMemoryCPUsNICs
50 GB64 GB81

Click a tab to view performance numbers for a standalone CipherTrust Manager or a two-node cluster with a load balancer.

UsersLatency (in ms)Requests/Second
1043.9716.21
2043.0132.51
3042.9348.42
4056.5363.45
5042.6680.83
6050.995.36
7045.54112.43
8047.02128.36
9065.12142.32
10068.99156.6
11068.81170.76
12079.2185.46
13070.51204.54
140100.1214.89
150131.71225.22
160125.13241.78
17084.51262.35
180104.14276.44
19099.66290.61
200127.36301.65
210136.48313.56
220143.68324.27
230245.09318.67
UsersLatency (in ms)Requests/Second
1045.0316.08
2044.0632.07
3044.2448.08
4044.0764.46
5044.4580.16
6044.9496.24
7046.61111.98
8045.69127.84
9045.87144.04
10045.62160.35
11046.03175.59
12046.11191.64
13047.04207.6
14048.32222.59
15048.6239.82
16046.87256.42
17050.69270.98
18052.53285.45
19053.97301.68
20051.31317.32
21054.71332.79
22055.66349.72
23052.44366.51
24054.63381.84
25056.22396.67
26067.06407.14
27074.4420.76
28078.71433.79
29074.36450.47
30073.85468.84
31075.46483.42
32075.96499.24
33079.52513.18
34088.56524.6
35077.46543.71
36084554.31
37095.23565
380100.92576.25
390102.75589.21
400103.8605.46
410124.6608.42
420132.51620.63
430141.22628.96
440166.33629.27
450191.44629.58
460216.55629.89

Comparison Graphs

Specification 2: Standalone vs Two-Node Cluster with Load Balancer

Physical Appliance

Server LocationClient Location
San Joseus-central1-a

CipherTrust Manager Configuration

System VolumeMemoryCPUsNICs
2 TB16 GB1 with 4 Cores1

Simulated the wrap requests for Google Workspace CSE on the CipherTrust Manager deployed on a physical appliance 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 sample for three runs.

UsersLatency (in ms)Requests/Second
1085.7215.3
2098.70530.165
30111.6945.03
40135.358.74
50158.9172.45
60177.0485.06
70195.1797.67
80229.715108.8
90264.26119.93

Comparison Graphs

Physical Appliance vs AWS Cloud vs Google Cloud

Recommendations

Assumption

Each user has 3 documents open and is editing them resulting in an autosave every 30 seconds, that is, 3/30=0.1 transactions per second (tps) per user.

Number of users = (throughput for around 200 ms latency)/0.1

Google Cloud

  1. Response time compliance of around 200 ms was met for a maximum throughput of 112.54 operations per second with a standalone CipherTrust Manager k170v instance with 4 CPUs and 16 GB RAM.

    The approximate number of users this configuration can handle is 1125.

  2. Response time compliance of around 200 ms was met for a maximum throughput of 198.03 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.

    The approximate number of users this configuration can handle is 1980.

  3. Response time compliance of around 200 ms was met for a maximum throughput of 231.91 operations per second with a standalone CipherTrust Manager k470v instance with 8 CPUs and 64 GB RAM.

    The approximate number of users this configuration can handle is 2319.

  4. Response time compliance of around 200 ms was met for a maximum throughput of 459.62 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.

    The approximate number of users this configuration can handle is 4596.

AWS Cloud

  1. Response time compliance of around 200 ms was met for a maximum throughput of 159.96 operations per second with a standalone CipherTrust Manager k170v instance with 4 CPUs and 16 GB RAM.

    The approximate number of users this configuration can handle is 1600.

  2. Response time compliance of around 200 ms was met for a maximum throughput of 304.81 operations per second with a two-node CipherTrust Manager k170v cluster (each node with 4 CPUs and 16 GB RAM) connected with an AWS load balancer.

    The approximate number of users this configuration can handle is 3048.

  3. Response time compliance of around 200 ms was met for a maximum throughput of 324.27 operations per second with a standalone CipherTrust Manager k470v instance with 8 CPUs and 64 GB RAM.

    The approximate number of users this configuration can handle is 3243.

  4. Response time compliance of around 200 ms was met for a maximum throughput of 629.58 operations per second with a two-node CipherTrust Manager k470v cluster (each node with 8 CPUs and 64 GB RAM) connected with an AWS load balancer.

    The approximate number of users this configuration can handle is 6296.

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.

Moreover, an increase in virtual users by roughly 140 percent is observed over CipherTrust Manager version 2.6.

On this page