Well while following links in this thread I came across a solution to the huge Hiberfil.sys file. If you only have 8 gb of RAM you Hiberfil.sys will be only 8GB! So no mater how much RAM you have like my case 16GB half of that is wasted space. this runs in advance CMD system32 powercfg.exe /hibernate /size 50 will cut the Hiberfil.sys to 8GB. that is a significant savings of space while still being covered for total loss of power.
Necrothreading...
My computer has 32GB of ram, and I'm about to double that. Just because. :) Anyway, using a 500GB SSD, that means my pagefile is at 32GB. That's about to double...just like my ram. That's NOT what I want. The assumption in a LOT of these recommendations is that ram is a small percentage of the hard drive size (whether it's a spinner or ssd).
Once I find out where W10 hides the pagefile settings, I'll be dropping it to 4GB.
Ken
Ive not come across any such apps so far. I know Photoshop used to need swapfile, not sure about later versions.
Pretty much the same situation here. Don't get me wrong, I'm not concerned about the space, but I have no applications that specifically need paging (by page file, I mean part of your hard disk being used to simulate extra RAM). I used to set the min/max values to an equal size equaling about a third of my system RAM. However since running x64 systems with 7 GB of RAM (so that's XP, Vista, and now 8), I now turn it off.
There DEFINITELY seems to be a visibile improvement in throughput. I mean heck, even if the system needs to create a page file when system RAM fills up, a SCSI HDD will still be slower than RAM. But the need for Windows to create the "emergency" paging file has only ever happened when I pushed the limits by opening multiple instances of applications with many files open. I filled up the system RAM to see what would happen. Towards the end, system stability became questionable as I could no longer open an app properly (without enough free RAM left). But until I got to 6.5 GB used, it was smoooooooth sailing.
And again, that was a test procedure. That never happens in day-to-day use. When I use Adobe Audition, it requires temp directories for it own audio caching, but since that's application specific, so I let the program deal with that.
Otherwise, I've had no problems with disabled paging for more than five years going. (The true answer is, it depends what you use it for).
You know what this reminds me of? Disabling Superfetch. I'll tell ya, perhaps it is more efficient by design to let Windows dynamically utilize unused RAM for disk and file caching. But my systems have ALWAYS improved in performance when I just allow for Prefectching. I think that Windows gets a bit bogged down when it has to decide what Superfetch memory to relinquish to the system, when another application or two is opened. So Windows needs to constantly re-evaluate how much RAM goes to applications VS Superfectch. I really seem to get a snappier system once Superfetch is disabled (only through the registry though. I never disable the Superfectch service, because that would kill Prefetching.)
:)
Quote