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

SAP Hold Your Own Key (HYOK) Resources

Performance summary

search

Performance summary

We have tested different environments to capture performance metrics for the CipherTrust Cloud Key Manager (CCKM) SAP HYOK integration. The performance results provided in this document demonstrate the effects of deployment choices on throughput for SAP HYOK key encrypt operations for a single key. This information can help you plan your CipherTrust Manager deployment to meet your performance needs for SAP HYOK integration.

All environments used an open source k6.io tool as the REST client to simulate decrypt requests from SAP HYOK keystores.

Note

  • Actual performance numbers in your environment may vary. Results can be affected by factors such as how and where CipherTrust Manager is deployed, CipherTrust Manager resources, the location of the cloud KMS, the chosen key source, network connectivity between CipherTrust Manager, the SAP HYOK cloud, and the key source, as well as traffic load balancing.

  • This document, may at times, abbreviate CipherTrust Manager as CM.

Tested environments

The following deployments were tested:

The following CipherTrust Manager release version was employed in the tested deployments:

DescriptionValue
Release version2.19

Test process

The test involved initiating a specified number of virtual users to execute decrypt operations on the SAP HYOK key. Each user simulated a separate thred. The overall test duration was 40 seconds for each measurement.

SAP HYOK deployment results

Ciphertrust Manager and K6 client are on-premises

8 CPU and 32 GB of RAM

AES 256

Here are the details of this deployment:

CM details

CM locationInstance typeCM configurationK6 configurationSource
SanJose labSingle instance8 CPU and 32 GB of RAM8 CPU, 64 GB of RAM, and 50 GB of HDDCipherTrust Manager

Results

Virtual usersRun time (seconds)Operations/secondsTime taken (P90) (seconds)
502582616456.403302/s11.72ms
1002741066852.293799/s23.29ms
5002906787266.610219/s132.08ms
10002245965614.615807/s374.35ms
15001817264542.750677/s616.21ms
20001429063572.175774/s901.43ms
25001401233502.709969/s1.39s
30001299073247.410589/s1.41s
35001343803256.95097/s1.99s
40001302103254.810601/s2.18s
45001253233132.726926/s3.24s
50001187202967.116548/s3.13s
RSA 3072

Here are the details of this deployment:

CM details

CM locationInstance typeCM configurationK6 configurationSource
SanJose labSingle instance8 CPU and 32 GB of RAM8 CPU, 64 GB of RAM, and 50 GB of HDDCipherTrust Manager

Results

Virtual usersRun time (seconds)Operations/secondsTime taken (P90) (seconds)
501565283913.040581/s20.6ms
1001525263812.714006/s49.08ms
5001507163767.640616/s337.02ms
10001504263760.349458/s664.3ms
15001475883689.546761/s900.07ms
20001476043689.767328/s1.17s
25001432573581.039336/s1.5s
30001435553588.491304/s1.72s
35001411363527.709941/s2.03s
40001335523338.011651/s2.45s
45001395363487.773784/s2.55s
50001394623485.846827/s2.78s
55001370313425.280997/s3.13s
60001351213370.446977/s3.38s
65001138492841.926664/s3.88s
7000776891941.661116/s5.25s
7500696001634.4521/s6.57
8000583431276.353584/s10.09s

16 CPU and 32 GB of RAM

AES 256

Here are the details of this deployment:

CM details

CM locationInstance typeCM configurationK6 configurationSource
SanJose labSingle instance16 CPU and 32 GB of RAM8 CPU, 64 GB of RAM, and 50 GB of HDDCipherTrust Manager

Results

Virtual usersRun time (seconds)Operations/secondsTime taken (P90) (seconds)
502172595431.33299/s12.87ms
1002683236707.796539/s21.26ms
5002862827156.852227/s127.3ms
10002009985024.60733/s502.76ms
15001798574495.42505/s769.97ms
20001544003859.338574/s1.36s
25001435653588.734/s1.75s
30001484233709.989953/s2.01s
35001376093439.595273/s2.61s
40001413713533.704276/s2.77s
RSA 3072

Here are the details of this deployment:

CM details

CM locationInstance typeCM configurationK6 configurationSource
SanJose labSingle instance16 CPU and 32 GB of RAM8 CPU, 64 GB of RAM, and 50 GB of HDDCipherTrust Manager

Results

Virtual usersRun time (seconds)Operations/secondsTime taken (P90) (seconds)
502719166797.700845/s11.19ms
1001338816644.027184/s45.34ms
5002802987038.788747/s398.47.ms
10001548273870.292993/s408.2ms
20002738286844.539846/s1.67s
30001935884839.315571/s5.49ms
40002372435930.963685/s7.25ms
50001420163549.93136/s3.48s
60002572726431.639269/s11.92ms
AES 256, Enable success audit events

Here are the details of this deployment:

CM details

CM locationInstance typeCM configurationK6 configurationSource
SanJose labSingle instance16 CPU and 32 GB of RAM8 CPU, 64 GB of RAM, and 50 GB of HDDCipherTrust Manager

Results

Virtual usersRun time (seconds)Operations/secondsTime taken (P90) (seconds)
501425803564.118546/s19.71ms
1001565393913.356442/s37.71ms
5001167562918.51705/s292.06ms
10001208953021.70154/s480.14ms
15001162752906.571097/s731.43ms
20001170772926.39078/s960.69ms
25001105772763.808288/s1.23s
30001076202690.143502/s1.63s
3500957762393.854873/s1.82s
4000944822344.96546/s2.6s
45001035492588.086671/s2.8s
5000940892323.381969/s3.47s
5500719841795.161082/s5.05s
6000814032034.587003/s5.17s
AES 256, disable success audit events

Here are the details of this deployment:

CM details

CM locationInstance typeCM configurationK6 configurationSource
SanJose labSingle instance16 CPU and 32 GB of RAM8 CPU, 64 GB of RAM, and 50 GB of HDDCipherTrust Manager

Results

Virtual usersRun time (seconds)Operations/secondsTime taken (P90) (seconds)
502172595431.33299/s12.87ms
1002683236707.796539/s21.26ms
5002862827156.852227/s127.3ms
10002009985024.60733/s502.76ms
15001798574495.42505/s769.97ms
20001544003859.338574/s1.36s
25001435653588.734/s1.75s
30001484233709.989953/s2.01s
35001376093439.595273/s2.61s
40001413713533.704276/s2.77s

Two node clusters of Ciphertrust Manager behind load balancer are on-premises and K6 client is also on-premises

16 CPU and 32 GB of RAM

Here are the details of this deployment:

CM details

CM locationInstance typeCM configurationK6 configurationSource
SanJose labSingle instance16 CPU and 32 GB of RAM8 CPU, 64 GB of RAM, and 50 GB of HDDCipherTrust Manager

Results

Virtual usersRun time (seconds)Operations/secondsTime taken (P90) (seconds)
502810717026.229607/s8.97ms
1003786629465.82768/s14.63ms
50052552613137.221485/s60.77ms
100042084410520.470685/s165.61ms
15003791489477.712357/s299.2ms
20003358138394.109008/s499.97ms
25003160247899.208216/s674.69ms
30003135917838.058786/s793.76ms
35002951717378.248556/s991.36ms
40002745066860.58453/s1.25s
45002731806827.267927/s1.45s
50002792616979.776071/s1.51s

32 CPU and 64 GB of RAM

Here are the details of this deployment:

CM details

CM locationInstance typeCM configurationK6 configurationSource
SanJose labSingle instance32 CPU and 64 GB of RAM8 CPU, 64 GB of RAM, and 50 GB of HDDCipherTrust Manager

Results

Virtual usersRun time (seconds)Operations/secondsTime taken (P90) (seconds)
503040727601.67745/s8.01ms
1003931659828.678428/s14.22ms
50056642314159.981913/s50.63ms
10003945009862.201022/s161.71ms
15003462028654.589461/s368.02ms
20003324888311.207163/s477.74ms
25002984447459.627745/s725.21ms
30002937017341.47043/s890.95ms
35002977447439.814009/s1.01s
40002669746672.6223742/s1.47s
45002797336991.902713/s1.38s
50002951077376.458011/s1.35s

Ciphertrust Manager is on AWS and K6 client is on GCP

8 CPU and 32 GB of RAM

Here are the details of this deployment:

CM details

CM locationInstance typeCM configurationK6 configurationSource
SanJose labSingle instance8 CPU and 32 GB of RAM8 CPU, 64 GB of RAM, and 50 GB of HDDCipherTrust Manager

Results

Virtual usersRun time (seconds)Operations/secondsTime taken (P90) (seconds)
1001142092853.6533.62ms
2001815284534.8847.61ms
3001890374725.0082.05ms
4001954284883.24122.84ms
5001910804774.52172.78ms
10001592053978.34485.72ms
20001300553250.211.15s
30001200922910.681.83s
40001037372591.683.47s
5000994712441.333.95s
6000934742118.545.25s
70001150372869.574.49s

16 CPU and 32 GB of RAM

Here are the details of this deployment:

CM details

CM locationInstance typeCM configurationK6 configurationSource
SanJose labSingle instance16 CPU and 32 GB of RAM8 CPU, 64 GB of RAM, and 50 GB of HDDCipherTrust Manager

Results

Virtual usersRun time (seconds)Operations/secondsTime taken (P90) (seconds)
1001215013035.9730.03ms
50040348310085.5347.14ms
6003591248976.06142.65ms
7002437276091.76284.62ms
8002142945355.68300.33ms
9001928714819.07390.03ms
10001896444739.45447.17ms
20001406933501.761.03s
30001443973413.921.58s
40001357543733.981.96s
50001430132246.751.73s

Conclusion

  • Increasing CipherTrust Manager RAM and CPU increases performance.

  • Increasing the number of nodes enhances performance.

  • The performance is better when the server and client are geographically close compared to when they are far apart.

  • Performance improves when success audit events are disabled compared to when they are enabled.

  • The performance is better with the AES key type compared to the RSA key type.

On this page