Yes, I'd like to know why I should put the pagefile on the SSD because I never really run out of ram.
When an application asks the OS for memory, the OS will give more than it asked for. This is because if the application asks for more memory, it's faster because the bookkeeping was already done so the OS gives it more memory. Of course, if the app continues to ask for more memory and this extra bit runs out, then the OS will do the same thing: give it more than it asked for.
It's like if you called up a restaurant to place a reservation to have a party with your friends. You don't really know how many will show up as some of them said "I might be able to go". So you do the sensible thing and reserve based on how many people are a definite yes and how many are a maybe in case they show up since it'll be easier to give them a seat rather than try to get the restaurant to pull in another table... which may not be available.
To go back to the computer, when Windows reserves memory for that application,
no other application can use it, even if the program doesn't actually use all of the space. Going back to the restaurant, it'd be like if you had say some seats left but the people who would take it are late. You'd probably be mad if the restaurant went "well you're not using these right now, so we'll give them to someone else." This reservation of memory is called a memory commit.
For the purposes of memory management in Windows, there's something called the virtual memory space, which is how much physical RAM you have plus how much space you set aside for the page file. The entire size of memory commits, or commit charge, must be able to fit in the virtual memory space. The thing with still needing a page file even though you don't run out of space in RAM is Windows can shuffle the unused commit memory into the page file when there's no free space left in RAM (free space is space that has literally not been touched yet or is marked as cached data). The page file is still accessed during this time.
This is also why you should
never remove the page file. What this does is it shrinks the virtual memory space to just physical RAM. This can lead to a situation where the commit charge exceeds the physical RAM size and some application will crash with an "out of memory" error because Windows can't commit any more memory. Except when you look at Task Manager, any memory commits not actually in use does not count towards memory usage, so it looks like you have a bunch of free RAM despite "running out"
Facebook
Twitter
Instagram