---
title: "DSM Accelerator [4.32] - Sept 05, 2024"
slug: "dsm-accelerator-4-32-sept-05-2024"
updated: 2026-08-19T06:39:42Z
published: 2026-08-19T06:39:42Z
canonical: "support.fortanix.com/dsm-accelerator-4-32-sept-05-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.32] - Sept 05, 2024

## 1. Overview

This document provides an overview of general improvements and resolved issues in the Fortanix Data Security Manager (DSM) Accelerator 4.32 release.

## 2. Improvements

- **DSM Accelerator Webservice:**
  - Added a new parameter, `AVAILABILITY`, which allows you to prioritize the cached key usage. You can continue using the cached key even if Fortanix DSM is not reachable when the time-to-live (TTL) for the cached key expires (**JIRA: PM-372**).

*For more details, refer to the* [*DSM Accelerator Webservice Developer Guide*](/v1/docs/dsm-accelerator-webservice-developer-guide)*.*
- **DSM Accelerator JCE Provider:**

*For more details, refer to the* [*DSM Accelerator JCE Provider Developer Guide*](/v1/docs/dsm-accelerator-jce-provider-developer-guide)*.*
  - Added a new parameter, `AVAILABILITY`, which allows you to prioritize cached key usage. You can continue using the cached key even if Fortanix DSM is not reachable when the time-to-live (TTL) for the cached key expires (**JIRA: PM-372**).

## 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 | 22,239/22,312 |
| AES 256: GCM Encryption/Decryption | 23,142/23,061 |
| AES 256: FPE Encryption/Decryption | 9,386/9,345 |

---

### 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 | 23,004/22,521 |
| AES 256: CFB Encryption/Decryption | 22,798/22,688 |
| AES 256: CTR Encryption/Decryption | 22,425/22,381 |
| AES 256: OFB Encryption/Decryption | 23,292/22,950 |
| AES 256: CCM Encryption/Decryption | 23,171/22,926 |