-
-
Scale and size considerations for deployments
-
-
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!
Scale and size considerations for deployments
Workspace Environment Management (WEM) is designed for large-scale enterprise deployments. When evaluating WEM for sizing and scalability, you need to consider database performance, Active Directory setup, firewall rules, and more.
WEM scalability is based on the number of agents and users. The more infrastructure servers available, the more agents and users WEM can support. The infrastructure servers synchronize various back-end components (SQL Server and Active Directory) with front-end components (administration console and agent).
Suppose that the machine where the infrastructure server is running uses the following specification:
- 4 vCPUs, 8 GB RAM, and 80 GB of available disk space.
You can use the following formula to calculate the number of the infrastructure servers required for your deployment. The formula is developed based on statistics related to certain customers:
- Number of infrastructure servers = (number of agents/1,000) + (number of users/3,000)
Note:
- In scenarios with NTLM authentication, certain performance issues have been observed with Workspace Environment Management 2006 and earlier. Those issues have not been observed when Kerberos authentication is used.
- No performance differences between NTLM authentication and Kerberos authentication have been observed with Workspace Environment Management 2006 and later.
- Starting with WEM 2212, agents download configuration data only when needed. This enhancement can reduce bandwidth consumption and the load on infrastructure services by up to 50%. See What’s new. We recommend that you upgrade your agents to 2212 or later so that you can reap the benefit.
Share
Share
In this article
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.