F5F Stay Refreshed Hardware Desktop Yes, it's acceptable to lower virtual RAM if needed.

Yes, it's acceptable to lower virtual RAM if needed.

Yes, it's acceptable to lower virtual RAM if needed.

Pages (2): Previous 1 2
J
JackeVillery
Junior Member
11
09-28-2023, 07:23 PM
#11
I've adjusted mine to 0 since I usually don't need it, and it helps preserve the lifespan of my SSD.
J
JackeVillery
09-28-2023, 07:23 PM #11

I've adjusted mine to 0 since I usually don't need it, and it helps preserve the lifespan of my SSD.

T
Tavado
Senior Member
505
09-28-2023, 11:22 PM
#12
This approach isn't ideal. Rather than allowing the OS to handle resource allocation, you should require each app to adjust its own settings. Not all programs are well-designed for this flexibility. Consider this: with 16 GB of RAM and 8 GB free, Chrome might assume only 6 GB is available. It would limit usage to avoid conflicts, storing less in memory and using a larger cache for inactive tabs. If only 6 GB remain, it would prioritize essential data and swap out less-used content. With 24 GB free, Chrome can allocate up to 20–24 GB, keeping more space for other tasks. Each time you switch tabs or open new ones, Chrome will dynamically assess available memory, discarding less-used items to free up space. It will also cache content more aggressively on disk, reducing reliance on the pagefile and improving speed. Pagefile handles background caching and persistence across restarts, storing frequently accessed files in RAM for quick access. Without it, resources remain in volatile memory, forcing apps to constantly seek data from slower storage or buffer changes. Additionally, system elements like Windows Explorer maintain cached icons and fonts in the pagefile, speeding up future launches. This setup enhances performance by balancing memory usage and persistence efficiently.
T
Tavado
09-28-2023, 11:22 PM #12

This approach isn't ideal. Rather than allowing the OS to handle resource allocation, you should require each app to adjust its own settings. Not all programs are well-designed for this flexibility. Consider this: with 16 GB of RAM and 8 GB free, Chrome might assume only 6 GB is available. It would limit usage to avoid conflicts, storing less in memory and using a larger cache for inactive tabs. If only 6 GB remain, it would prioritize essential data and swap out less-used content. With 24 GB free, Chrome can allocate up to 20–24 GB, keeping more space for other tasks. Each time you switch tabs or open new ones, Chrome will dynamically assess available memory, discarding less-used items to free up space. It will also cache content more aggressively on disk, reducing reliance on the pagefile and improving speed. Pagefile handles background caching and persistence across restarts, storing frequently accessed files in RAM for quick access. Without it, resources remain in volatile memory, forcing apps to constantly seek data from slower storage or buffer changes. Additionally, system elements like Windows Explorer maintain cached icons and fonts in the pagefile, speeding up future launches. This setup enhances performance by balancing memory usage and persistence efficiently.

Pages (2): Previous 1 2