SSD being eaten by pagefile and hiberfile

Associate
Joined
31 Mar 2013
Posts
753
Location
Essex/london


I only have a 128gb SSD and these 2 files are taking almost 30gb... Why are they so big? How can i fix this?
 
They will need to be at least the same size as the amount of RAM you have in the computer.

Either remove some RAM, buy a bigger SSD or disable hibernation and investigate reducing the pagefile size if it's appropriate to your usage.
 
Either remove some RAM, buy a bigger SSD or disable hibernation and investigate reducing the pagefile size if it's appropriate to your usage.

WTF - REMOVE SOME RAM ?!!!!!!!!!!!!!!!!!!!!!

What have you been smoking dude ? :eek:

Move pagefile to secondary harddrive and delete the old pagefile. Turn off hibernation. Done
 
It's a valid suggestion. An unlikely one I admit, but valid nonetheless.

Maybe the OP needs 16GB, maybe he doesn't. Most gaming rigs get by just fine on 4GB.
 
The required space would shrink, may require reconfiguring to shrink it though. Unsure about Windows 8 as I refuse to use it, earlier Windows versions default the pagefile size to 1.5x the amount of physical RAM.
 
hibernate usually matches total ram size
pagefile, when system managed is usually set to 1.5x total ram, this can increase up to 2x ram size (and never goes back down to 1.5) if you accidentally use too much ram at some point.

Makes it impossible to install windows with 32GB ram with a small 64/80GB SSD as it leaves itself no space on first boot and throws a blue screen, very smart :P

I agree with the above posts, disable hibernate and manually set the page file to around 2GB (but leave it on the SSD)
 
Move pagefile to secondary harddrive and delete the old pagefile.


-25

seriously. it's not good advice. you want your pagefile on the fastest disk. it certainly doesn't do SSDs any harm if that's what you think.

http://blogs.msdn.com/b/e7/archive/2009/05/05/support-and-q-a-for-solid-state-drives-and.aspx

Should the pagefile be placed on SSDs?

Yes. Most pagefile operations are small random reads or larger sequential writes, both of which are types of operations that SSDs handle well.

In looking at telemetry data from thousands of traces and focusing on pagefile reads and writes, we find that

Pagefile.sys reads outnumber pagefile.sys writes by about 40 to 1,
Pagefile.sys read sizes are typically quite small, with 67% less than or equal to 4 KB, and 88% less than 16 KB.
Pagefile.sys writes are relatively large, with 62% greater than or equal to 128 KB and 45% being exactly 1 MB in size.

In fact, given typical pagefile reference patterns and the favorable performance characteristics SSDs have on those patterns, there are few files better than the pagefile to place on an SSD.

reduce the size by all means but keep it on the SSD.
 
-25

seriously. it's not good advice. you want your pagefile on the fastest disk. it certainly doesn't do SSDs any harm if that's what you think.

http://blogs.msdn.com/b/e7/archive/2009/05/05/support-and-q-a-for-solid-state-drives-and.aspx

reduce the size by all means but keep it on the SSD.

-100

When you have 16+gigs of RAM and your secondary drive is a slower SSD.

After the initial app commits the pagefile is virtually never touched again so what a waste of resources.
 
page file is just backup hen you have that much memory. put in on a HDD, or disable it entirely.

Similarly, you have things like back and restore, your user folders ('My Documents', 'My Pictures') which can be relocated, and also your temporary folder (Internet cache, temp folder in your environment variables, ect...). All those take space on your SSD, that don't really need to be there.

I've used WinDirStats to analyse my SSD content and relocate the biggest offenders. It take sa while to analyse, but it[s something you run once, or when your SSD space is being eaten up. Now my SSD is 1/2 full.
 
Back
Top Bottom