pagefile.sys file is 50gb

[anskaz]

how can i reduce the size?

[mtono]

my win 11 pro pagefile is 1075 mb. no problems so far. i never changed it. 1075 mb is default in my case.
byebye

[A&A]

The Page File only makes sense to be manually set if it needs to be changed from dynamic to static, otherwise Windows does the job pretty well already.

[Illusion of Progress]

引用自 Bad 💀 Motha：

Well I have had it set to 8GB MIN 32GB MAX for like 10 years on ALL PCs now so it's never a problem.

And that's great, but irrelevant.

I'm not saying that you, personally, need a page file larger than you are setting it for.

I'm saying that the values you are recommending, because "it works for me", isn't necessarily good enough for everyone else. If you can't ensure that they will be, you should not be advocating that others should make said changes.

There's a distinction, and you should be able to differentiate the two.

[Bad 💀 Motha]

Yes it is fine to do it how I do it. Why? Because that's how I go about it that's why.

I don't give a crap what you all deem as correct. That's your problem.

Don't want to sound mean but everytime I say anything on here some know it all had to step over me. Just stop doing that. If you don't like what I've suggested then ignore it and move on.

What I recommend is fine and users can try it. If it doesn't work for them then they can try other settings. It's not as if I'm recommending something that's going to hurt your PC some how or brick your OS.

[Illusion of Progress]

Nobody is telling you what to do or not to do for yourself.

It becomes a different story when you suggest, advise, or instruct others that they should do something when no necessary need has arisen to make said changes, and something that can have adverse effects when set incorrectly.

Again, that's the distinction I said you were missing.

If you're more concerned with others ignoring what you say if they disagree with it, even when it may be wrong, than you are that others might follow what you say and end up in a bad situation... then your priorities are all wrong. I don't disagree with you all too often (this page file subject is probably one of the only ones I consistently do) so I can't help you with any of those other times. But telling others to just ignore you isn't the solution to that problem.

引用自 Bad 💀 Motha：

It's not as if I'm recommending something that's going to hurt your PC some how or brick your OS.

Maybe we have different criteria here, but a user session going South when programs or even the operating system start crashing or the possibility of data loss arises, all because of a commit limit quota that is too restrictive is enforced, then yes, I consider that something that would hurt things. No, it won't lose you the operating system, and previously established data won't (likely) be lost or corrupted, but "only" losing unsaved data in the current user session can still be very bad.

[Bad 💀 Motha]

Well again I never suggested to use the 1GB min / max setting. In all seriousness if you wanted something low just put it back to AUTO and click SET and reboot the PC to apply the change.

But overall I was suggesting that the user must have done something and they have but did not remember doing it and that's why they ended up with the pagefile taking up approx 50GB of space on C Drive.

If anything the OP should probably just put it back to OS default of Auto and once you click Set and Restart the OS. Do some things on the PC that are very demanding / intensive on it as a stress test and see how it does.

Overall it's probably best to leave the pagefile on auto UNLESS there is a real reason to change it. And I'd you do change it. Be prepared to set the MIN to around 0.5X your installed RAM and the MAX to around 1.5X your installed ram. To ensure there is enough of a minimum for the commit charge.

One reason for when I manually changed mine to 32GB MIN and MAX on a few PCs was to help avoid the physical allocation on the drive changing over time for the file. But I suppose I was over thinking it by doing that since fragmentation is not a big deal on an SSD like it is on a HDD

[Illusion of Progress]

引用自 Bad 💀 Motha：

One reason for when I manually changed mine to 32GB MIN and MAX on a few PCs was to help avoid the physical allocation on the drive changing over time for the file. But I suppose I was over thinking it by doing that since fragmentation is not a big deal on an SSD like it is on a HDD

The fragmentation thing in practice wasn't as big of a deal as it sounded like it could be in theory, even on HDDs, at least in the latter years (think Windows XP through Windows 7 days; maybe back in the Win 9x days it was?), but yes if you you wanted to min-max it on an HDD you'd probably want to set a fixed size.

With SSDs that's certainly not relevant anymore.

[_I_]

on a hdd with slow heads/seek times and low cache, fragmented files might cause stuttering or slower loading
on newer drives, with faster seek times and high rpm, fragmented files are not a problem, it wll be able to read the file faster than its needed, or faster than the sata controller can take it anyway

ssd all sectors have the same seek time, and it makes no difference if a file is spread all over the drive or not, its seq read for the file is not any different