By using this site, you agree to our Privacy Policy and our Terms of Use. Close
Pemalite said:
WolfpackN64 said:

Linux, FreeBSD and anything based on XNU really.

Especially XNU's memory managment is far surperior to Microsoft's, being able to run from a desktop to a watch without much problem and without RAM spikes that go up to 9GB's while no applications are visably open.

Can't say I have ever seen Windows spike memory usage up to 9GB in my 20 years of WIndows usage. Right now Windows is using 4GB with 5GB cached out of 32GB.

Windows and *Nix based OS's are vastly different in how they handle memory anyway, so they aren't directly comparable.

For instance, *Nix based OS's like Android, Chrome OS etc' will use all the available Ram to cache as much data as possible... The bonus of that is everything always feels quick and snappy.
But if you are working with 10+ Gigabytes large data sets, it can take time to free that memory up and flush it to disk.

Plus if you are working with say... A Web Browser with a crap ton of tabs... And you start to get low on memory, the OS will start to unload tabs, which means you have to reload the pages that get unloaded later. Not exactly always ideal.

Windows on the other hand will just let you keep on going... As it will just page the data to disk once memory is full... And with SSD's as fast as they are these days, it's not necessary to unload tabs.

There are pro's and cons to each approach... And it's really dependent on what you want out of the system. But Windows 10 isn't the same as the terrible Vista or 9x OS's. Could it be better? Shit yes. There is always room for improvement. Same goes for *Nix.

The spike's were irregular, but it did happen. When it happened during a game, it would simply crash the game AND briefly crash the entire Windows desktop. I was not the only one with this problem and I managed to resolve it by killing all the background apps. Which is something I shouldn't do normally, but when you have apps like "Camera", "Calender" and "Xbox" taking in rescources when they're not needed at all is just bad design.