Windows 10 is a memory hog

[dawindbag]

I installed W10 JTP on an old desktop machine that I don't use a lot and it's on the low end of the specs spectrum. W10 slows it to a crawl. It's got 3GB of memory and at idle with just Chrome open I'm using 96% of my memory. This is on a clean install, Win 8.1 ran just fine.

 

[umangpop777]

I am also using it on my old machine of 2Gb ram and 2Ghz dual core processor. But it is working fine (as compared to Windows 7). But Windows 10 build 9841 was working quite better than 9926. I don't know why

 

[rhapdog]

I'm using it on my laptop which has 6GB RAM, and 4267MB is in use. That's with Excel open, KeePass2, Thunderbird, and 13 Chrome tabs open. Never really got over 1.5GB used when using 8.1 before with this little open. As a matter of fact, I've had a whole lot more open and always had trouble getting the machine to utilize 4GB before (back when I was running a 16GB desktop on 8.1).

It's most likely because they haven't worked on the memory management as much yet, as they are still doing UI changes. Memory management should be in place by the time of the consumer release.

 

[David Feifer]

There are also a few services and debugging that is running in the background that wont be there once windows 10 goes live. Also since Cortana is new in this build we have no idea how much resources she is taking up.

 

[rhapdog]

Good point about Cortana. I wonder if I turn off her "listening" so that I don't have "Hey Cortana" if memory resources will go down? I may test that later.

 

[anon(8150199)]

Also, I noticed that the cached memory is not returned back to RAM, so when I run a guest OS, the cache will keep increasing.