The following notes describe how the Decrypt pool Size function should be set and used.
The primary reason to introduce this function is to improve the download time that is taken up by the decrypt process, when calling the HSM. This process is outside the control of KeyScaler Software.
A multi-threaded approach is developed for this decryption part of the process. This help to reduce the download times when downloading large data files from the Secure Repos. This pool size only applies to Secure Repo data decryption if decryption has is enabled in the secure repository.
The implementation of the feature is controllable via a setting in kms.properties file. The setting is called:
By default, this value is set to 4. Which means that the software will use 4 threads to when performing the decrypt function.
The feature can be switch off by setting the value to 0. This will set the software back to decryption as it was prior to this patch, that is, no multi-threading being used.
The maximum value the number of threads will be determined by the number of processors available on the server. However, it is not advised to set this value too high as this would limit resources to other processes.
Advisory note, it is not recommended to set the value size to 1, as this would not provide any additional treading benefits but still adds additional overhead to the process.