-
License Administration Console
-
Improve performance by specifying thread use
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Improve performance by specifying thread use
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 starts 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. After 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:
- Maximum Number of License Server Manager Processing Threads to 30.
- 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
Set License Server thread use
- In the top right corner of the console, select Administration.
- Select the Server Configuration tab and the License Server Configuration bar.
- Change the Maximum Number of License Server Manager Processing Threads and Maximum Number of License Server Manager Receiving Threads fields (up to 999 threads).
- Restart the Citrix Licensing service.
Set web server thread use
Use this procedure to set the maximum number of threads that the web server for the License Administration Console uses to process requests. Specify a larger number if you expect many users to access the console simultaneously.
- In the top right corner of the console, click Administration.
- Click the Server Configuration tab and the Web Server Configuration bar.
- Modify the Maximum Number of Web Server Threads field (up to 999 threads).
- Restart the Citrix Licensing service.
Share
Share
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.