I only put it on StarMade Universe as a courtesy to the owner. He\'s the one who went and changed the link on the wiki page to point there instead of ocean-of-storms. I was a little annoyed, but figured it was the \"tax\" for hosting the SMEdit documentation on his wiki.
Windows is a pig. What\'s worse is it hides how much memory it uses. Ever run excel? It claims to only use 125K of memory, even when you have a several megabyte spreadsheet loaded. It\'s the crap you get when the company who owns the O/S owns the apps. But I\'m an old 1-2-3 guy and I\'m digressing into bitterness.
Anyway, the \"half your memory\" is a bit misleading. Windows itself takes a big chunk. But the rest is hard to measure. There\'s this thing called \"virtual memory\" where a program \"thinks\" is has a whole bunch of memory. But what\'s going on is that only some of it is loaded into physical memory. The rest is on the disk in something called a \'swap partition\'. When your program asks for it, it\'s loaded off of disk into physical memory. So just looking at the amount of physical memory free can be misleading. It could just be what\'s loaded in memoy of the virtual stuff. Or what\'s still swapped in that hasn\'t been swapped out yet. The 50% is more likely due to whatever algorithm Windows uses to decide when to swap things in or out.
This is why it always ends up being trial and error to work out what the best settings are.
Windows is a pig. What\'s worse is it hides how much memory it uses. Ever run excel? It claims to only use 125K of memory, even when you have a several megabyte spreadsheet loaded. It\'s the crap you get when the company who owns the O/S owns the apps. But I\'m an old 1-2-3 guy and I\'m digressing into bitterness.
Anyway, the \"half your memory\" is a bit misleading. Windows itself takes a big chunk. But the rest is hard to measure. There\'s this thing called \"virtual memory\" where a program \"thinks\" is has a whole bunch of memory. But what\'s going on is that only some of it is loaded into physical memory. The rest is on the disk in something called a \'swap partition\'. When your program asks for it, it\'s loaded off of disk into physical memory. So just looking at the amount of physical memory free can be misleading. It could just be what\'s loaded in memoy of the virtual stuff. Or what\'s still swapped in that hasn\'t been swapped out yet. The 50% is more likely due to whatever algorithm Windows uses to decide when to swap things in or out.
This is why it always ends up being trial and error to work out what the best settings are.