{"id":1669,"date":"2020-04-21T07:05:19","date_gmt":"2020-04-21T07:05:19","guid":{"rendered":"http:\/\/neu.koetzingit.de\/ab-sofort-mehr-performance-fuer-server-2016-und-2019\/"},"modified":"2026-06-02T13:32:49","modified_gmt":"2026-06-02T13:32:49","slug":"ab-sofort-mehr-performance-fuer-server-2016-und-2019","status":"publish","type":"post","link":"https:\/\/www.koetzingit.de\/en\/ab-sofort-mehr-performance-fuer-server-2016-und-2019\/","title":{"rendered":"Better performance for Server 2016 and 2019, starting now?"},"content":{"rendered":"

W<\/span>While I was recently searching the internet for information on Server 2016 performance issues, I came across an interesting article from Microsoft explaining a new optimization in Windows. This new feature has actually been around since Windows 7, but it has been further developed and was only enabled by default in the Windows 10 client version. Unlike the client version, this feature was disabled in the 2016 and 2019 server editions, but it can be enabled via a simple PowerShell command. Unfortunately, I couldn\u2019t find any information about this feature in the context of multi-user systems (Remote Desktop Services). So I wondered whether this feature might also enable an immediate improvement in performance or user experience on session hosts. Some of my clients are currently testing this, and I\u2019m waiting for their results. Would you like to do the same?<\/p>\n

<\/p>\n

\u201eWhat function is that?\" you ask. The function is called \"Memory Compression<\/strong>\u201cand is enabled by default in Windows 10. Open Windows Task Manager, go to Performance, then Memory, and you\u2019ll find:\u00a0in use (compressed)<\/strong>.<\/span><\/p>\n

\"Blog<\/p>\n

Which memory is compressed, and how can this improve performance on a session host? Compressed memory is the memory area that would have been written to the page file but is instead stored compressed in memory; that is, instead of being stored uncompressed on the hard drive, it is stored compressed in memory. According to Microsoft, Windows can compress and decompress very efficiently and quickly, making it significantly faster than writing to or reading from the hard drive. The Windows operating system begins paging immediately, regardless of how much RAM is available. When Windows experiences \u201estress\u201c with RAM (\u201estress\u201c is a term used by Microsoft, and I believe I once read that this occurs at approximately 70% RAM usage), Windows writes significantly more to the swap file. This results in the CPU also being under greater load. In this case as well helps compress the RAM<\/strong>, since compressed data is now stored on the hard drive<\/span> are written in compressed form rather than uncompressed. This results in fewer and shorter read and write operations.<\/div>\n
\u00a0
<\/span><\/div>\n
File servers, print servers, mail servers, etc., will not benefit from RAM compression because their RAM usage patterns are not highly dynamic; this is why the feature has been disabled. As we all know, multi-user systems (Remote Desktop Services) behave more like multiple workstations, with many applications and greater dynamics when it comes to memory usage. Therefore, session hosts utilize paging significantly more, and thus also benefit from using memory compression.<\/div>\n
\u00a0<\/div>\n
Microsoft states the following:
<\/span><\/div>\n
\u201cThe new memory compression concepts should help make Windows 10 appear snappier and more responsive<\/strong> than earlier versions, even on existing hardware.\u201d<\/em> <\/span><\/div>\n
\u00a0<\/div>\n
I am convinced that the same applies to multi-user systems and should be enabled by default when the RDS role is installed!
<\/span><\/div>\n
\u00a0<\/div>\n
Memory compression can be enabled using the following PowerShell command: Enable-MMagent -MemoryCompression<\/strong> This means that a restart is not necessary, <\/b>not even with active users on the system. Depending on RAM usage, the compressed portion in Task Manager should increase.
<\/span><\/div>\n

\u00a0<\/p>\n

\"Blog<\/p>\n

Since the previous screenshot, I've enabled compression and opened a few applications. There is still plenty of RAM available (17.6 GB), but Windows has started paging, this time compressed into RAM!<\/strong><\/span>
<\/span><\/p>\n

What do you think? Let me know if you've tried Memory Compression! I'm curious to hear about your experiences with Memory Compression!
<\/span><\/p>\n

\u00a0<\/p>\n

References\u00a0<\/span><\/h3>\n