Requests come in to the license server through a listener port. All communication must be accepted by an acceptance thread. If the message is accepted, a receive thread handles it and then a processing thread processes it. To improve license server performance when receiving a large number of requests, you can configure the maximum number of receive and processing threads to use.
When a program initiates an I/O request (an example would be a request to check-out a license), it creates and uses a thread. The thread maintains the place and data in the program as a reference point, and once the request is complete, the program can be re-entered at the same point. You can have many requests at the same time, depending upon how many threads are allowed. This is called multi-threading.
The optimal values needed for acceptable license server performance are dependent on the hardware, the site configuration, and the request volume. If you set the limits too high and your hardware cannot support it, it will slow down the communication. If you set the limits too low, it will take longer for the communication to occur as the system will wait until it can create more threads before it executes incoming requests. You should test and evaluate different values to determine the configuration that meets your site's needs. A good starting point for a large scale deployment might be setting the Maximum Number of License Server Manager Processing Threads to 30 and the Maximum Number of License Server Manager Receiving Threads to 15.
There are two areas where you can specify the thread limits:
- License Server
- Web Server