-
-
-
Memory Management
-
-
Automatically back up configuration sets using WEM APIs and Windows PowerShell
-
Manage DaaS-provisioned non-domain-joined machines using WEM
-
Protect Citrix Workspace environments using process hierarchy control
-
Troubleshoot VDA registration and session launch issues using scripted tasks
-
Use Windows events as triggers to detect VDA registration issues
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!
Memory Management
These settings let you optimize application memory usage through Workspace Environment Management (WEM).
Memory management
If these settings are turned on, WEM calculates how much memory a process is using and the minimum amount of memory a process needs without losing stability. WEM considers the difference as excess memory. When the process becomes idle, WEM releases the excess memory that the process consumes to the page file, and optimizes the process for subsequent launches. Usually, an application becomes idle when it is minimized to the task bar.
When applications are restored from the task bar, they initially run in their optimized state but can continue to consume additional memory as needed.
Similarly, WEM optimizes all applications that users are using during their desktop sessions. If there are multiple processes over multiple user sessions, all memory that is freed up is available for other processes. This behavior increases user density by supporting a greater number of users on the same server.
Optimize Memory Usage for Idle Processes. Forces processes that remain idle for a specified time to release excess memory until they are no longer idle.
Idle Sample Time (min). Lets you specify the length of time that a process is considered idle after which it is forced to release excess memory. During this time, WEM calculates how much memory a process is using, and the minimum amount of memory a process needs, without losing stability. The default value is 120 minutes.
Idle State Limit (percent). Lets you specify the percentage of CPU usage below which a process is considered idle. The default is 1%. We recommend that you do not use a value greater than 5%. Otherwise, a process being actively used can be mistaken for idle, causing its memory to be released.
Do Not Optimize When Total Available Memory Exceeds (MB). Lets you specify a threshold limit below which WEM optimizes memory usage for idle applications.
Exclude Processes from Memory Usage Optimization. Lets you exclude processes from memory usage optimization. Specify the process name, for example, notepad.exe.
WEM does not optimize application memory usage for the following system processes:
rdpshellwfshellrdpclipwmiprvsedllhostaudiodgmsdtcmscorsvwspoolsvsmsswinlogonsvchosttaskmgrSystem Idle ProcessSystemLSASSwininitmsiexecservicescsrssMsMpEngNisSrvMemory Compression
Memory usage limit
Enable Memory Usage Limit for Specific Processes. Lets you limit the RAM usage of a process by setting an upper limit for the RAM, the process can consume.
Warning:
Applying memory usage limits to certain processes might have unintended effects, including slow system responsiveness.
-
Add. Allows you to add a process to which you want to apply a memory usage limit.
-
Remove. Allows you to delete an existing item.
-
Edit. Allows you to edit an existing item.
-
Dynamic Limit. Allows you to apply a dynamic limit to the specified process. This setting dynamically limits the amount of RAM allocated to the specified process. If applied, enforces memory usage limits depending on the available memory. Therefore, the RAM that the specified process consumes might exceed the specified amount.
-
Static Limit. Allows you to apply a static limit to the specified process. This setting always limits the amount of RAM allocated to the specified process. If applied, restricts the process from consuming more than the specified amount of memory regardless of the amount of available memory. As a result, the RAM that the specified process consumes is capped at the specified amount.
To add a process:
-
On the Administration Console > System Optimization > Memory Management > Memory Usage Limit tab, click Add.
-
In the Add Process window, type the name of the process you want to add (for example, notepad.exe.), configure the memory usage limit, select a limit mode from the drop-down menu, and then click OK.
To edit an item, select the item and click Edit.
To remove an item, select the item and click Remove.
To apply a dynamic limit to an item, select the item and click Dynamic Limit.
To apply a static limit to an item, select the item and click Static Limit.
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.