Page 1 of 1

Stability Primocache in Windows 10

Posted: Sat Aug 22, 2015 11:40 am
by suserg2
Hello!
How can affect the changes introduced in the memory manager squeeze pages of RAM for Windows 10 on a stable work Primocache?
Details on the work of the compression of memory pages is explained here:
http://www.tenforums.com/windows-10-new ... ssion.html

Re: Stability Primocache in Windows 10

Posted: Sun Aug 23, 2015 3:15 pm
by minhgi
You shouldn't have the worry about so much about this new compression technology. Just use the same setting that you have always been using with Primocache. Just by visual observation in Windows 10 task manager, the Cpu usage is slightly higher when it is doing its compression. I think it kick in when you have about 1/4 of the total memory left. My primocache, including system usage, is about the 3.5 GB out the total 8. Somewhere around 6GB usage, my cpu spike for a bit.

Anyway, I don't see concern about it, but seem to work well with Primocache. It just make your computer able to open apps.

Re: Stability Primocache in Windows 10

Posted: Mon Aug 24, 2015 8:48 am
by suserg2
Thanks for the advice. I worry not only for the volume of free RAM (from 16GB), and impact on the work in the modified algorithm Primocache memory manager. Microsoft itself is not going to take into account the specifics of the disk-caching programs when changing memory management algorithm.

Re: Stability Primocache in Windows 10

Posted: Fri Aug 28, 2015 4:16 am
by Davey126
Running PrimoCache v2 under Win 10 x64 Pro for nearly a month with no issues both in 'normal' use and when resources were under pressure. Observed read hit rate is somewhat lower than in previous Windows versions which I attribute to the compression algorithms built into Win 10. Confirmed by temporarily disabling Superfetch while troubleshooting another issue which also disabled memory compression. Read hit rates returned to Win 8.1 levels. Deferred writes work as before. Liking Win 10 memory management. Better use of free ram with no degradation in responsiveness when launching new applications. MS got it right (although it took a couple cumulative fixes to iron out a post launch bug).