Requests come in to the license server through a listener port. An acceptance thread must accept all communication. If the message is accepted, a receive thread handles it and then a processing thread processes it. To improve license server performance when receiving many 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. Once the request is complete, the program can be reentered at the same point. You can have many requests at the same time, depending upon how many threads are allowed. This technique is called multithreading.
The optimal values needed for acceptable license server performance 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 slows down the communication. If you set the limits too low, it takes longer for the communication to occur. The system waits until it can create more threads before it executes incoming requests. Test and evaluate different values to determine the configuration that meets your site needs. A good starting point for a large-scale deployment might be setting:
There are two areas where you can specify the thread limits:
- License Server
- Web server