1. Overview
This article provides an overview of the improvements and Performance Statistics in the Fortanix Data Security Manager (DSM) Accelerator 5.10 release.
DSM Accelerator Webservice version - 1.36
2. Improvement
DSM Accelerator Webservice:
Improved DSMA-WS to update the cached bearer token with the valid bearer token provided in the API call when the cached token expires (JIRA: ES-635).
For more information, refer to the DSM Accelerator Webservice Developer Guide.
3. Fortanix Data Security Manager Accelerator Performance Statistics
3.1 Runtime Environment
NOTE
The following table lists the standard recommended runtime environment. You can choose a higher configuration for better performance.
DSM Accelerator was run in the runtime environment listed below for performance testing.
Item | Specification |
|---|---|
Number of Cores | 4 |
CPU | Intel(R) Xeon(R) CPU E5-2673 v4 @ 2.30GHz |
RAM | 2 GiB |
VM Type | Standard D4ds v4 Azure VM |
Docker Runtime Configuration |
|
3.2 DSM Accelerator Webservice
NOTE
The performance numbers below are captured with a single node; if you need higher performance or throughput, then Fortanix recommends adding multiple nodes.
Key Types and Operations | Throughput (Operations/second on a 1-node cluster re-using a single TLS session) |
|---|---|
AES 256: CBC Encryption/Decryption | 19,853/19,642 |
AES 256: GCM Encryption/Decryption | 20,695/20,180 |
AES 256: FPE Encryption/Decryption | 9,429/9,341 |
3.3 Additional Modes
Key Types and Operations | Throughput (Operations/second on a 1-node cluster re-using a single TLS session) |
|---|---|
AES 256: CBCNOPAD Encryption/Decryption | 20,585/20,315 |
AES 256: CFB Encryption/Decryption | 20,646/20,263 |
AES 256: CTR Encryption/Decryption | 20,679/20,299 |
AES 256: OFB Encryption/Decryption | 20,705/20,321 |
AES 256: CCM Encryption/Decryption | 20,636/20,234 |