3 ms·
I'm sure page files make sense. But if a page-file starts freezing applications regularly for seconds with typical settings and hardware, all while there is sti
by coffeeaddicted 14y ago
I'm sure page files make sense. But if a page-file starts freezing applications regularly for seconds with typical settings and hardware, all while there is still sufficient main-memory, there seems to be some rework necessary indeed.
- barrkel 14y agoI've never had page file activity "freezing applications regularly for seconds" since the late 90s. I'm not sure what's causing what you're talking about; it sounds like a dodgy hard drive.
- coffeeaddicted 14y agoNot dodgy, just a sleeping hard drive. Modern HD's sleep when unused and take that long to wake up - that's not really unusual. People just don't notice that as much if they have a single HD as that is usually active most of the time you are working. But with 2 HD's (typical SSD + HDD combination) you often have one HD sleeping and will run into this a lot more thereby. There's ways to work around it - putting the page file on the HD which is more active or not allowing the HD to sleep as often. But my favorite would still be to simply prevent Windows from even using the page-file before the memory is at least used up to 50% - which would nearly never happen on my system for example.
- barrkel 14y agoI don't let my HDDs sleep for this very reason (my main drive is indeed SSD). Your heuristic would fail pretty badly on my machine; faced with an allocation for 8GB (not unusual for my utilities), I would have to wait while about 6GB of memory is paged out. That latency would be far worse than any delays from paging.