--- title: "DSM Accelerator [4.31] - Aug 06, 2024" slug: "dsm-accelerator-4-31-aug-06-2024" updated: 2026-08-19T06:39:47Z published: 2026-08-19T06:39:47Z canonical: "support.fortanix.com/dsm-accelerator-4-31-aug-06-2024" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.fortanix.com/llms.txt > Use this file to discover all available pages before exploring further. # DSM Accelerator [4.31] - Aug 06, 2024 ## 1. Overview This article provides an overview of general improvements and resolved issues in the Fortanix Data Security Manager (DSM) Accelerator 4.31 release. ## 2. Improvements and Bug Fixes - **DSM Accelerator JCE Provider:** - A new variant of the DSM Accelerator JCE Provider Thin client is now created as a single unified JAR that contains the Fortanix dependencies (`sdkms-client` and `dsm-accelerator`) (**JIRA: PROD-8857**). *For more details, refer to the following documents:* - [*DSM Accelerator JCE Provider Deployment Guide*](/v1/docs/dsm-accelerator-jce-provider-deployment-guide) - [*DSM Accelerator JCE Provider Downloads*](/v1/docs/dsm-accelerator-downloads-dsm-accelerator-jce-provider) - Improved the key retrieval process in the DSM Accelerator JCE Provider to utilize the cached data more efficiently (**JIRA: PROD-8799**). - Fixed the `NoPadding` scheme for the DSM Accelerator JCE Provider where the ciphertext length correctly matches the input length (**JIRA: ES-385**). ## 3. Fortanix Data Security Manager Accelerator Performance Statistics ### 3.1 Runtime Environment > [!NOTE] > 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 | `docker run -d --network host --memory=1g --memory-swap=2g --log-driver json-file --log-opt max-size=100m` | --- ### 3.2 DSM Accelerator Webservice > [!NOTE] > NOTE > > The performance numbers below are captured with a single node; if you need higher performance or throughput, then we recommend 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 | 21,381/20,712 | | AES 256: GCM Encryption/Decryption | 22,057/21,736 | | AES 256: FPE Encryption/Decryption | 9,464/9,470 | --- ### 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 and Decryption | 21,336/21,441 | | AES 256: CFB Encryption/Decryption | 22,013/21,471 | | AES 256: CTR Encryption/Decryption | 21,853/21,728 | | AES 256: OFB Encryption/Decryption | 22,221/21,864 | | AES 256: CCM Encryption/Decryption | 21,720/21,216 |