I used all the mentioned points and was able to sign using NetHSM and the driver and took a pressure test, but a few points caught my attention in the pressure test:
1- The machine in which the driver is used does not go under load
2- The NetHSM container cannot use all the cores of its host and only uses one core. I told it to use 2 cores while running NetHSM, but it didn’t change. Did you limit the use of CPU in your configs?
3- If we increase the number of clients in the pressure test by Apache benchmark, we will encounter an error after 2 or 3 tests and NetHSM will stop working. I have sent a photo of the error in the attachment. What is the cause?
What is the cause of the problems and is there a way to solve it?
we have already talked about this through the support. But for the sake of completeness let me summarize the outcome here, too.
Generally the container currently is not production-ready, this means errors like the one you reported are to be expected. We are also working towards a more stable container (software-only) release - but this may still take some more time.
If you are looking for a faster solution or a more specific solution for your particular use-case feel free and approach us - we are also offering paid development services for NetHSM.
However, I tried to get the NetHSM software part from the source build from the link below, but I encountered errors in the config.ml, some of the errors were resolved, but the error is still there. Can you guide me in this matter?
