Microsoft DKE Service Performance Summary
We have tested different environments to capture performance metrics for the CipherTrust Cloud Key Manager (CCKM) Microsoft Double Key Encryption (DKE) integration. The performance results provided within this document demonstrate the effects of deployment choices on throughput for Microsoft DKE key encrypt operations for one key. This can help you plan your CipherTrust Manager deployment to meet your performance needs for Microsoft DKE integration.
All environments used an open source k6.io tool as the REST client to simulate DKE decrypt requests from Microsoft clients.
Note
Actual performance numbers in your environment may be different. The results can vary based on factors, such as how and where the CipherTrust Manager is deployed, CipherTrust Manager resources, the location of cloud KMS, the key source of your choice, the network connectivity between the CipherTrust Manager, Microsoft DKE Cloud and your key source, as well as how the traffic is load balanced.
Tested Environments
The following deployments were tested:
The following CipherTrust Manager release version was employed in the tested deployments:
| Description | Value |
|---|---|
| Release version | 2.17.0.12772 RC8 |
Test Process
The test consisted of starting a given number of virtual users to perform decrypt operations on the Microsoft DKE key. Each user simulated a separate thread. The total test duration was 40 seconds for each reading.
Microsoft DKE Deployment Results
CipherTrust Manager and K6 Client are on Azure
Endpoint is Configured with Email for Authentication and Tenancy is a Single Tenant
4 CPU 16 GB
Here are the details of this deployment:
CM Details
| CM Environments | Volume | CPU | Memory | Authentication | Tenancy |
|---|---|---|---|---|---|
| Ciphertrust manager (Azure) | 50 GB | 4 | 16 GB | Single-tenant |
K6 Details
| K6 | Volume | CPU | Memory |
|---|---|---|---|
| K6 client (Azure) | 50 GB | 8 | 64 GB |
Results
| Virtual Users | Run time (seconds) | Operations/seconds | Time taken (P90) (seconds) |
|---|---|---|---|
| 500 | 40 | 301.437757/s | 2.63s |
| 1000 | 40 | 299.336473/s | 5.34s |
| 1500 | 40 | 286.958765/s | 8.13s |
| 2000 | 40 | 289.461286/s | 10.8s |
| 2500 | 40 | 285.693796/s | 13.45s |
| 3000 | 40 | 290.192717/s | 15.97s |
| 3500 | 40 | 285.395626/s | 18.28s |
| 4000 | 40 | 287.976997/s | 20.87s |
| 4500 | 40 | 280.316827/s | 23.62s |
| 5000 | 40 | 273.656447/s | 27.03s |
| 5500 | 40 | 277.925966/s | 28.65s |
| 6000 | 40 | 275.795028/s | 30.81s |
8 CPU 64 GB
Here are the details of this deployment:
CM Details
| CM Environments | Volume | CPU | Memory | Authentication | Tenancy |
|---|---|---|---|---|---|
| Ciphertrust manager (Azure) | 50 GB | 8 | 64 GB | Single-tenant |
K6 Details
| K6 | Volume | CPU | Memory |
|---|---|---|---|
| K6 client (Azure) | 50 GB | 8 | 64 GB |
Results
| Virtual Users | Run time (seconds) | Operations/seconds | Time taken (P90) (seconds) |
|---|---|---|---|
| 1000 | 40 | 937.675929/s | 1.85s |
| 2000 | 40 | 930.176183/s | 3.65s |
| 3000 | 40 | 915.361911/s | 5.47s |
| 4000 | 40 | 920.848429/s | 7.21s |
| 5000 | 40 | 891.392166/s | 8.91s |
| 6000 | 40 | 912.013307/s | 10.96s |
| 7000 | 40 | 880.133286/s | 11.93s |
| 8000 | 40 | 828.393022/s | 14.77s |
| 9000 | 40 | 867.000752/s | 16.21s |
| 10000 | 40 | 845.180123/s | 17.7s |
| 11000 | 40 | 863.657284/s | 19.43s |
| 12000 | 40 | 835.209459/s | 21.12s |
| 13000 | 40 | 837.793345/s | 22.68s |
| 14000 | 40 | 821.588673/s | 27.73s |
| 15000 | 40 | 848.569653/s | 24.86s |
| 16000 | 40 | 796.251779/s | 28.48s |
| 17000 | 40 | 845.339293/s | 27.73s |
| 18000 | 40 | 840.190566/s | 31.07s |
Endpoint is Configured with Role for Authentication and Tenancy is a Single Tenant
4 CPU 16 GB
Here are the details of this deployment:
CM Details
| CM Environments | Volume | CPU | Memory | Authentication | Tenancy |
|---|---|---|---|---|---|
| Ciphertrust manager (Azure) | 50 GB | 4 | 16 GB | Single-tenant |
K6 Details
| K6 | Volume | CPU | Memory |
|---|---|---|---|
| K6 client (Azure) | 50 GB | 8 | 64 GB |
Results
| Virtual Users | Run time (seconds) | Operations/seconds | Time taken (P90) (seconds) |
|---|---|---|---|
| 100 | 40 | 53.630582/s | 2.18s |
| 200 | 40 | 59.175574/s | 3.83s |
| 300 | 40 | 58.878411/s | 6.16s |
| 400 | 40 | 59.956688/s | 8.47s |
| 500 | 40 | 61.097801/s | 10.07s |
| 600 | 40 | 52.194668/s | 12.34s |
| 700 | 40 | 60.851934/s | 15.85s |
| 800 | 40 | 60.160831/s | 17.76s |
| 900 | 40 | 61.000974/s | 18.4s |
| 1000 | 40 | 59.017757/s | 21.24s |
| 1100 | 40 | 52.311081/s | 25.49s |
| 1200 | 40 | 58.560716/s | 27.32s |
| 1300 | 40 | 58.480499/s | 31.26s |
| 1400 | 40 | 59.495208/s | 31.13s |
| 1500 | 40 | 53.849506/s | 35.52s |
8 CPU 64 GB
Here are the details of this deployment:
CM Details
| CM Environments | Volume | CPU | Memory | Authentication | Tenancy |
|---|---|---|---|---|---|
| Ciphertrust manager (Azure) | 50 GB | 8 | 64 GB | Single-tenant |
K6 Details
| K6 | Volume | CPU | Memory |
|---|---|---|---|
| K6 client (Azure) | 50 GB | 8 | 64 GB |
Results
| Virtual Users | Run time (seconds) | Operations/seconds | Time taken (P90) (seconds) |
|---|---|---|---|
| 100 | 40 | 155.264383/s | 0.70467s |
| 200 | 40 | 167.261439/s | 1.4s |
| 300 | 40 | 186.299285/s | 1.88s |
| 400 | 40 | 190.738639/s | 2.56s |
| 500 | 40 | 195.074869/s | 3.22s |
| 600 | 40 | 189.460485/s | 3.99s |
| 700 | 40 | 193.936023/s | 4.56s |
| 800 | 40 | 193.141467/s | 5.4s |
| 900 | 40 | 189.179328/s | 6.24s |
| 1000 | 40 | 196.241641/s | 6.72s |
| 1100 | 40 | 197.318683/s | 7.18s |
| 1200 | 40 | 185.490272/s | 8.45s |
| 1300 | 40 | 193.260793/s | 8.93s |
| 1400 | 40 | 197.195079/s | 9.54s |
| 1500 | 40 | 194.877367/s | 10.36s |
| 1600 | 40 | 191.214409/s | 10.92s |
| 1700 | 40 | 195.7723/s | 12.52s |
| 1800 | 40 | 194.425864/s | 12.22s |
| 1900 | 40 | 190.945904/s | 13.26s |
| 2000 | 40 | 183.069893/s | 15.88s |
| 2100 | 40 | 176.345674/s | 16.17s |
| 2200 | 40 | 179.927429/s | 17.05s |
| 2300 | 40 | 174.719055/s | 17.49s |
| 2400 | 40 | 159.231921/s | 19.79s |
| 2500 | 40 | 194.822666/s | 16.32s |
| 2600 | 40 | 194.743725/s | 18.3s |
| 2700 | 40 | 194.027697/s | 18.41s |
| 2800 | 40 | 194.879586/s | 18.3s |
| 2900 | 40 | 192.62135/s | 19.79s |
| 3000 | 40 | 193.702672/s | 19.72s |
| 3100 | 40 | 194.560084/s | 20.89s |
| 3200 | 40 | 184.324798/s | 23.03s |
| 3300 | 40 | 176.172311/s | 24.36s |
| 3400 | 40 | 175.881082/s | 26.16s |
| 3500 | 40 | 178.067138/s | 27.75s |
| 3600 | 40 | 178.211371/s | 27.37s |
| 3700 | 40 | 178.958189/s | 27.12s |
| 3800 | 40 | 185.275967/s | 29.97s |
| 3900 | 40 | 176.689299/s | 28.46s |
| 4000 | 40 | 176.275521/s | 29.53s |
| 4100 | 40 | 190.282555/s | 32.44s |
Endpoint is Configured with Email for Authentication and Tenancy is Multi-Tenant
4 CPU 16 GB
Here are the details of this deployment:
CM Details
| CM Environments | Volume | CPU | Memory | Authentication | Tenancy |
|---|---|---|---|---|---|
| Ciphertrust manager (Azure) | 50 GB | 4 | 64 GB | Multi-tenant |
K6 Details
| K6 | Volume | CPU | Memory |
|---|---|---|---|
| K6 client (Azure) | 50 GB | 8 | 64 GB |
Results
| Virtual Users | Run time (seconds) | Operations/seconds | Time taken (P90) (seconds) |
|---|---|---|---|
| 500 | 40 | 300.181058/s | 2.67s |
| 1000 | 40 | 299.918426/s | 5.31s |
| 1500 | 40 | 294.132794/s | 8.08s |
| 2000 | 40 | 289.965496/s | 10.81s |
| 2500 | 40 | 286.458949/s | 13.41s |
| 3000 | 40 | 283.362494/s | 16.37s |
| 3500 | 40 | 278.552601/s | 18.76s |
| 4000 | 40 | 284.638515/s | 21.21s |
| 4500 | 40 | 277.40887/s | 23.78s |
| 5000 | 40 | 272.968213/s | 26.16s |
| 5500 | 40 | 272.015562/s | 28.35s |
| 6000 | 40 | 274.789761/s | 31.29s |
Two Node Cluster of CipherTrust Manager Behind Load Balancer is on Azure and K6 Client is also on Azure
Endpoint is Configured with Email for Authentication and Tenancy is a Single Tenant
4 CPU 16 GB
Here are the details of this deployment:
CM Details
| CM Environments | Volume | CPU | Memory | Authentication | Tenancy |
|---|---|---|---|---|---|
| Ciphertrust manager (Azure) | 50 GB | 4 | 16 GB | Single-tenant | |
| Ciphertrust manager (Azure) | 50 GB | 4 | 16 GB | Single-tenant |
K6 Details
| K6 | Volume | CPU | Memory |
|---|---|---|---|
| K6 client (Azure) | 50 GB | 8 | 64 GB |
Results
| Virtual Users | Run time (seconds) | Operations/seconds | Time taken (P90) (seconds) |
|---|---|---|---|
| 500 | 40 | 560.264145/s | 1.4s |
| 1000 | 40 | 555.098356/s | 2.9s |
| 1500 | 40 | 556.247198/s | 4.35s |
| 2000 | 40 | 553.644946/s | 5.79s |
| 2500 | 40 | 546.547801/s | 7.21s |
| 3000 | 40 | 533.344865/s | 8.83s |
| 3500 | 40 | 542.116026/s | 10.18s |
| 4000 | 40 | 537.286016/s | 11.52s |
| 4500 | 40 | 528.792471/s | 13.19s |
| 5000 | 40 | 522.948107/s | 14.59s |
| 5500 | 40 | 523.668554/s | 15.97s |
| 6000 | 40 | 511.027996/s | 17.51s |
| 6500 | 40 | 520.72448/s | 18.64s |
| 7000 | 40 | 520.155642/s | 20s |
| 7500 | 40 | 517.077489/s | 21.38s |
| 8000 | 40 | 503.220529/s | 23.21s |
| 8500 | 40 | 508.716794/s | 24.17s |
| 9000 | 40 | 509.640573/s | 25.46s |
| 9500 | 40 | 502.812361/s | 26.56s |
| 10000 | 40 | 501.981745/s | 28.02s |
| 10500 | 40 | 497.643986/s | 29.44s |
| 11000 | 40 | 499.265302/s | 30.83s |
8 CPU 64 GB
Here are the details of this deployment:
CM Details
| CM Environments | Volume | CPU | Memory | Authentication | Tenancy |
|---|---|---|---|---|---|
| Ciphertrust manager (Azure) | 50 GB | 8 | 64 GB | Single-tenant | |
| Ciphertrust manager (Azure) | 50 GB | 8 | 64 GB | Single-tenant |
K6 Details
| K6 | Volume | CPU | Memory |
|---|---|---|---|
| K6 client (Azure) | 50 GB | 8 | 64 GB |
Results
| Virtual Users | Run time (seconds) | Operations/seconds | Time taken (P90) (seconds) |
|---|---|---|---|
| 1000 | 40 | 1785.9656/s | 0.92194s |
| 2000 | 40 | 1775.972033/s | 1.87s |
| 3000 | 40 | 1784.329928/s | 2.85s |
| 4000 | 40 | 1767.921883/s | 3.81s |
| 5000 | 40 | 1765.264588/s | 4.71s |
| 6000 | 40 | 1737.042021/s | 5.79s |
| 7000 | 40 | 1736.97193/s | 6.56s |
| 8000 | 40 | 1720.903737/s | 7.42s |
| 9000 | 40 | 1730.427238/s | 8.4s |
| 10000 | 40 | 1694.106053/s | 9.6s |
| 11000 | 40 | 1717.985554/s | 10.02s |
| 12000 | 40 | 1687.344706/s | 11.23s |
| 13000 | 40 | 1696.308474/s | 12.14s |
| 14000 | 40 | 1674.624243/s | 13.01s |
| 15000 | 40 | 1664.104646/s | 13.68s |
| 16000 | 40 | 1700.759239/s | 14.58s |
| 17000 | 40 | 1657.510241/s | 14.9s |
| 18000 | 40 | 1649.916413/s | 16.2s |
| 19000 | 40 | 1670.585066/s | 17.39s |
| 20000 | 40 | 1580.920728/s | 18.8s |
| 21000 | 40 | 1663.647103/s | 18.68s |
| 22000 | 40 | 1644.084146/s | 19.67s |
| 23000 | 40 | 1652.460077/s | 20.79s |
| 24000 | 40 | 1661.632755/s | 21.42s |
| 25000 | 40 | 1638.396322/s | 21.99s |
| 26000 | 40 | 1669.657113/s | 23.79s |
| 27000 | 40 | 1675.61502/s | 24.65s |
| 28000 | 40 | 1632.48011/s | 26.35s |
| 29000 | 40 | 1720.746917/s | 28.08s |
| 30000 | 40 | 1749.691725/s | 29.54s |
| 31000 | 40 | 1751.657854/s | 31.23s |
Endpoint is Configured with Role for Authentication and Tenancy is a Single Tenant
4 CPU 16 GB
Here are the details of this deployment:
CM Details
| CM Environments | Volume | CPU | Memory | Authentication | Tenancy |
|---|---|---|---|---|---|
| Ciphertrust manager (Azure) | 50 GB | 4 | 16 GB | Single-tenant | |
| Ciphertrust manager (Azure) | 50 GB | 4 | 16 GB | Single-tenant |
K6 Details
| K6 | Volume | CPU | Memory |
|---|---|---|---|
| K6 client (Azure) | 50 GB | 8 | 64 GB |
Results
| Virtual Users | Run time (seconds) | Operations/seconds | Time taken (P90) (seconds) |
|---|---|---|---|
| 100 | 40 | 94.809402/s | 1.23s |
| 200 | 40 | 106.746964/s | 2.12s |
| 300 | 40 | 110.958677/s | 3.08s |
| 400 | 40 | 111.646216/s | 4.16s |
| 500 | 40 | 108.70752/s | 6.15s |
| 600 | 40 | 114.558865/s | 6.46s |
| 700 | 40 | 116.371723/s | 8.14s |
| 800 | 40 | 119.106371/s | 8.99s |
| 900 | 40 | 112.805089/s | 10.12s |
| 1000 | 40 | 109.298707/s | 11.94s |
| 1100 | 40 | 107.992884/s | 12.64s |
| 1200 | 40 | 108.048609/s | 14.92s |
| 1300 | 40 | 110.887416/s | 14.96s |
| 1400 | 40 | 114.051035/s | 15.83s |
| 1500 | 40 | 109.996097/s | 18.37s |
| 1600 | 40 | 111.554102/s | 18.17s |
| 1700 | 40 | 112.078401/s | 19.47s |
| 1800 | 40 | 111.540947/s | 21.78s |
| 1900 | 40 | 110.845966/s | 22.07s |
| 2000 | 40 | 105.897333/s | 22.07s |
| 2100 | 40 | 108.613549/s | 25.66s |
| 2200 | 40 | 113.923375/s | 27.89s |
| 2300 | 40 | 109.004526/s | 27.63s |
| 2400 | 40 | 115.152758/s | 28.93s |
| 2500 | 40 | 116.424596/s | 31.83s |
8 CPU 64 GB
Here are the details of this deployment:
CM Details
| CM Environments | Volume | CPU | Memory | Authentication | Tenancy |
|---|---|---|---|---|---|
| Ciphertrust manager (Azure) | 50 GB | 8 | 64 GB | Single-tenant | |
| Ciphertrust manager (Azure) | 50 GB | 8 | 64 GB | Single-tenant |
K6 Details
| K6 | Volume | CPU | Memory |
|---|---|---|---|
| K6 client (Azure) | 50 GB | 8 | 64 GB |
Results
| Virtual Users | Run time (seconds) | Operations/seconds | Time taken (P90) (seconds) |
|---|---|---|---|
| 500 | 40 | 322.479723/s | 1.86s |
| 1000 | 40 | 348.214688/s | 3.81s |
| 1500 | 40 | 348.34051/s | 6.04s |
| 2000 | 40 | 343.04312/s | 7.82s |
| 2500 | 40 | 344.602226/s | 9.1s |
| 3000 | 40 | 317.581956/s | 12.05s |
| 3500 | 40 | 332.000826/s | 13.59s |
| 4000 | 40 | 336.267234/s | 16.46s |
| 4500 | 40 | 331.868606/s | 17.68s |
| 5000 | 40 | 338.895869/s | 24.42s |
| 5500 | 40 | 302.98068/s | 25.3s |
| 6000 | 40 | 331.355614/s | 27.52s |
| 6500 | 40 | 349.681425/s | 25.72s |
| 7000 | 40 | 340.685515/s | 27.79s |
| 7500 | 40 | 360.236346/s | 29.75s |
| 8000 | 40 | 357.52348/s | 30.08s |
CipherTrust Manager is on GCP and K6 Client is on Azure
Endpoint is Configured with Email for Authentication and Tenancy is a Single Tenant
4 CPU 16 GB
Here are the details of this deployment:
CM Details
| CM Environments | Volume | CPU | Memory | Authentication | Tenancy |
|---|---|---|---|---|---|
| Ciphertrust manager (Azure) | 50 GB | 4 | 16 GB | Single-tenant |
K6 Details
| K6 | Volume | CPU | Memory |
|---|---|---|---|
| K6 client (Azure) | 50 GB | 8 | 64 GB |
Results
| Virtual Users | Run time (seconds) | Operations/seconds | Time taken (P90) (seconds) |
|---|---|---|---|
| 500 | 40 | 260.2973/s | 2.99s |
| 1000 | 40 | 256.590559/s | 5.96s |
| 1500 | 40 | 243.25712/s | 9.51s |
| 2000 | 40 | 250.244478/s | 12.17s |
| 2500 | 40 | 247.967538/s | 14.92s |
| 3000 | 40 | 247.076747/s | 18.03s |
| 3500 | 40 | 243.288222/s | 21.39s |
| 4000 | 40 | 244.278415/s | 21.86s |
| 4500 | 40 | 237.021952/s | 27.02s |
| 5000 | 40 | 234.741217/s | 30.23s |
| 5500 | 40 | 234.381174/s | 32.61s |
| 6000 | 40 | 233.126993/s | 35.48s |
8 CPU 64 GB
Here are the details of this deployment:
CM Details
| CM Environments | Volume | CPU | Memory | Authentication | Tenancy |
|---|---|---|---|---|---|
| Ciphertrust manager (Azure) | 50 GB | 8 | 64 GB | Single-tenant |
K6 Details
| K6 | Volume | CPU | Memory |
|---|---|---|---|
| K6 client (Azure) | 50 GB | 8 | 64 GB |
Results
| Virtual Users | Run time (seconds) | Operations/seconds | Time taken (P90) (seconds) |
|---|---|---|---|
| 500 | 40 | 510.370788/s | 1.56s |
| 1000 | 40 | 518.692451/s | 3.1s |
| 1500 | 40 | 531.513091/s | 4.53s |
| 2000 | 40 | 507.708349/s | 6.25s |
| 2500 | 40 | 516.785705/s | 7.76s |
| 3000 | 40 | 508.697681/s | 9.28s |
| 3500 | 40 | 520.425672/s | 10.38s |
| 4000 | 40 | 514.879573/s | 12.21s |
| 4500 | 40 | 507.13912/s | 13.58s |
| 5000 | 40 | 514.0577/s | 14.49s |
| 5500 | 40 | 500.345548/s | 16.55s |
| 6000 | 40 | 486.665809/s | 18.6s |
| 6500 | 40 | 487.280281/s | 20.36s |
| 7000 | 40 | 475.944149/s | 21.75s |
| 7500 | 40 | 448.630315/s | 24.57s |
| 8000 | 40 | 425.585925/s | 28.32s |
| 8500 | 40 | 449.065649/s | 27.64s |
| 9000 | 40 | 446.422804/s | 29.14s |
| 9500 | 40 | 455.652378/s | 28.89s |
| 10000 | 40 | 562.003657/s | 31.58s |
Endpoint is Configured with Role for Authentication and Tenancy is a Single Tenant
4 CPU 16 GB
Here are the details of this deployment:
CM Details
| CM Environments | Volume | CPU | Memory | Authentication | Tenancy |
|---|---|---|---|---|---|
| Ciphertrust manager (Azure) | 50 GB | 4 | 16 GB | Role | Single-tenant |
K6 Details
| K6 | Volume | CPU | Memory |
|---|---|---|---|
| K6 client (Azure) | 50 GB | 8 | 64 GB |
Results
| Virtual Users | Run time (seconds) | Operations/seconds | Time taken (P90) (seconds) |
|---|---|---|---|
| 100 | 40 | 48.735364/s | 2.21s |
| 200 | 40 | 52.68879/s | 4.44s |
| 300 | 40 | 52.566259/s | 7.28s |
| 400 | 40 | 51.853057/s | 9.83s |
| 500 | 40 | 54.051404/s | 12.23s |
| 600 | 40 | 53.137674/s | 16.09s |
| 700 | 40 | 53.612458/s | 17.28s |
| 800 | 40 | 53.061575/s | 19.53s |
| 900 | 40 | 52.831731/s | 23.73s |
| 1000 | 40 | 51.697063/s | 25.47s |
| 1100 | 40 | 51.767529/s | 28.53s |
| 1200 | 40 | 50.743934/s | 32.31s |
8 CPU 64 GB
Here are the details of this deployment:
CM Details
| CM Environments | Volume | CPU | Memory | Authentication | Tenancy |
|---|---|---|---|---|---|
| Ciphertrust manager (Azure) | 50 GB | 8 | 64 GB | Role | Single-tenant |
K6 Details
| K6 | Volume | CPU | Memory |
|---|---|---|---|
| K6 client (Azure) | 50 GB | 8 | 64 GB |
Results
| Virtual Users | Run time (seconds) | Operations/seconds | Time taken (P90) (seconds) |
|---|---|---|---|
| 100 | 40 | 93.474111/s | 1.11s |
| 200 | 40 | 103.787319/s | 2.2s |
| 300 | 40 | 102.171858/s | 3.66s |
| 400 | 40 | 102.008771/s | 4.91s |
| 500 | 40 | 103.090055/s | 5.98s |
| 600 | 40 | 105.757206/s | 7.52s |
| 700 | 40 | 108.194733/s | 8.23s |
| 800 | 40 | 106.201338/s | 9.63s |
| 900 | 40 | 107.481191/s | 10.95s |
| 1000 | 40 | 105.898062/s | 12.76s |
| 1100 | 40 | 106.44994/s | 13.46s |
| 1200 | 40 | 107.833901/s | 14.53s |
| 1300 | 40 | 107.569803/s | 16.12s |
| 1400 | 40 | 107.973984/s | 15.85s |
| 1500 | 40 | 109.84268/s | 17.71s |
| 1600 | 40 | 111.927588/s | 19.01s |
| 1700 | 40 | 105.118502/s | 22.54s |
| 1800 | 40 | 105.31122/s | 21.63s |
| 1900 | 40 | 107.110964/s | 23.07s |
| 2000 | 40 | 107.210351/s | 24.49s |
| 2100 | 40 | 108.42108/s | 22.93s |
| 2200 | 40 | 105.44603/s | 28.79s |
| 2300 | 40 | 99.709105/s | 32.03s |
Conclusion
Increasing CM RAM and CPU increases the performance.
Increasing the number of nodes enhances the performance.
The performance is better when the endpoint is configured with the email as compared to the role.
When the email is being used with a single tenant and multitenant, there is no major difference in the performance.
The performance is better when the when server and client are geographically closed as compared to far.
Sizing the Environment
To size the environment, you must evaluate the peak traffic of DKE by establishing the maximum number of requests hitting the DKE infrastructure. The following factors must be considered.
The number of total users.
The geographic distribution and flexibility in working hours.
Suppose a 100k users company named ABC is located in a one-time zone only. All of its employees have a shift from 9 am to 5 pm. So, there might be 95k users opening one particular DKE-protected email or document within 5 minutes at the start of their shift, which is 320 requests per second. The peaks likely exceed 1000 requests per second.
But suppose a 100k users company named XYZ is evenly distributed among 10 different time zones across the world. All of its employees have flexible working hours. A document opened at the start of their shift may be opened by 10k users in a 20-minute window, which is 10 requests per second. The peaks are likely below 50 requests per second.
The usage of DKE in the protection of emails and documents. On an hourly basis, a user may open 20 DKE-protected emails and up to 2 DKE-protected documents.
Accessing the DKE templates and client configuration offline.
If a DKE-protected email thread or document is available offline for 7 days, opening it will result in one request per user.
If the offline caching is disabled, editing the same email thread or document may result in several requests per hour. At least one request each time the same user opens same the email or document.
The number of total DKE-protected emails or documents opened by the average user on a daily basis.
If only the most sensitive content is DKE-protected, an average ABC user may access 2 DKE-protected emails or documents per day. It will generate 200k requests per day, which is less than 10 requests per second.
If all emails and documents are DKE-protected, the 100k users of XYZ can access 50 DKE-protected emails or documents per day. It may generate nearly 200 requests per second even with offline access, which is likely 500 requests without offline access.
To ensure high availability, DKE infrastructure must be fault-tolerant, behind a network load balancer.
If you already have the Managed Service Providers, a good way to estimate the load is by checking the number of documents accessed with the highest classifications like Strictly Confidential.
