The command “Get-MMagent” will retrieve the current configuration, which can be used to validate if memory compression is running.Īn important note, as shown in the screenshot, when enabling memory compression, page combining is also automatically enabled. Memory compression is disabled by default on the Server operating system and can be enabled by running the following PowerShell command “Enable-MMagent -Memor圜ompression”. The memory compression process is hidden from the task manager but visible for both PowerShell and Process Explorer.
Since the introduction memory compression was running on the background but became a separate process since Windows 1607. Memory compression was introduced in Windand Windows Server 2016. To get all the details it is really recommend reading the full article, which can be found here. The required data are extracted from the RAM faster even though additional CPU resources are spent to compress/decompress them. It helps to reduce the number of read / write requests to the memory pages in the slow (compared to RAM) paging file on a hard drive. The compressed memory feature is designed to improve the performance (responsiveness) of the system due to storing part of the memory pages in RAM in a compressed form.
shared an excellent description of memory compression. It is important to start with a correct understanding of memory compression. But is there any performance value when enabling memory compression, or does it come with a performance penalty? This research will take a closer look and will show the real value of memory compression in a Citrix Virtual Apps scenario. Since the release of Windows 10 and Windows Server 2016, Microsoft implemented memory compression, which is by default disabled on the server operating systems, but enabled on Windows 10. Performance is a very important factor of the success of a virtual desktop environment.
0 kommentar(er)
