How to handle memory overflow in Manor Lords?
Once my city population crossed the 5,000 mark, zooming the camera would trigger a total freeze for about three seconds—the input lag was absolutely brutal. My 16GB of G.Skill Trident Z RGB DDR4 3600 was pegged at 92-96% utilization, forcing the system to lean on the slow hell that is disk-based virtual memory. I tried using some 'memory cleaner' software to flush the RAM, but the usage just spiked back instantly and crashed the game to desktop. That was a wake-up call that superficial cleaning is useless. I went into System Advanced Properties and manually set the virtual memory to a fixed range of 24GB-32GB, hosting it on my fastest NVMe partition. Checking Resource Monitor, the commit charge expanded from 18GB to 28GB, and those jarring zoom stutters vanished. I actually messed up the first time by leaving it on 'System Managed,' which caused page file resizing stutters until I locked the value. RAM temps stayed around 45-51℃ with VRMs at 58-63℃. Performance Analyzer shows the swap frequency has plummeted, and the experience is finally snappy.
