In this web content, the author explores a feature implemented by Microsoft that limits the amount of memory a process can use. The author highlights several issues with this feature: it was not documented, it does not actually save memory, and it can result in high CPU costs. The author shares their investigation into a Chrome performance problem caused by this feature and discusses the abnormal amount of time spent in KiPageFault, a function triggered when a process accesses memory that is not in its working set. Surprisingly, the author discovers that setting the process to background mode caps the working set at 32 MiB, causing a significant slowdown. The author criticizes this functionality and suggests that it should be removed.
https://randomascii.wordpress.com/2023/10/01/32-mib-working-sets-on-a-64-gib-machine/#more-4032