Avatar of BzowK
BzowK
Flag for United States of America asked on

Suggested Page File Settings for Specific System with SSD & 8gb RAM

Good Morning All -

I've got a Samsung Ultrabook Series 9 NP900X3A which I've had for about a month and love.  The only thing I'd like to have different is more drive space, but they haven't released a 256GB mSata drive yet for retail purchase.

Here are the specs:
-  Intel i5 1.6Ghz Proc
- 8 GB RAM (Fastest BUS will allow)
- 128GB SSD (1 large partition + 1 200mb partition that Win7 makes upon setup)
- Windows 7 x64 Pro

Currently, I have the paging file set for it to be automatically managed and uses about 8gb on the SSD.  The configuration I use on all other systems with SSD is to add a large phyical drive, use the paging file on it only, and make it as big as reccomended - however - I don't have the space in this ultrabook.

Question
I've read a lot of different articles that say different things about what to do with your paging file (with an SSD) for the best performance, but they all vary.  My question is - Especially given my system specs, what is the best setting for my paging file?  

Some people have even said not to use one if you have enough RAM.  I usually wouldn't mess with it, but am trying to free up space and if it's recommended that I do not use one, the extra 8 gb would be great to have.

Thanks!
StorageWindows 7Hardware

Avatar of undefined
Last Comment
John

8/22/2022 - Mon
ASKER CERTIFIED SOLUTION
John

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
pgm554

The page file is a leftover from the old windows swap file days.
Basically it's purpose was when you exceeded your RAM  capacity,it used your disk as RAM.
As a secondary function it served as a memory dump area in case of a crash.
Nether of these are very relevant or necessary anymore.

If you want to save space,I would set the swap file at maybe 2 gigs and be done with it.

It really shouldn't hurt anything.
xema

An old rule of thumb regarding the swap file was 1.5 times youre physical memory, now a days it's exagerated.

As we're talking of a small sized HD I'll do as pgm554 recomended a 2 GB swap file size,
But I'll go a little further, make the  initial size and the maximun size the same. I'll restart the sistem and perform a HD defragmentation.
It may sound exagerated with win 7, but that way the file will be cataloged as non movible.
BzowK

ASKER
Thanks - even though the final answers seemed consistant, the opinions varied even with all posts here - interesting.

I'll try setting it at 2gb for now - at least until another post saying otherwise is made - but don't agree with the HDD defrag.  It is an SSD you know - Thanks
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23
xema

BenKellerman;
As I said, it may sound exagerated.  But I've seen speed improvements by doing so with Win XP and Vista.
I know thad SSD HD's are fast but at the end they behave as a "normal" HD.
But I respect your opinion.
pgm554

I used to set my swap file to static (initial the same as max) as as it made some sense in that hard disks upon boot up,would have to create the swap file dynamically,but with an SSD,you really don't see any performance hit.

15 second boot ,15 second shutdown on my laptop these days.

And no,it's not a good idea to defrag.
In fact make sure it's turned off in W7.
Trim support should take care of disk maintenance issues.
John

There isn't much to choose between the first two answers, and they are consistent. Your choice between 4 or 2 Gb. I would also refrain from defragging an SSD.
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
Callandor

>I know thad SSD HD's are fast but at the end they behave as a "normal" HD.

This is not true.  Random access times are 100x faster, since there are no moving parts, and sequential throughput can go up to 500MB/sec, something a hard disk can't do.  You do not want to defrag an SSD because 1) the SSD access doesn't improve - there's no moving head latency and 2) there's a limited number of write cycles for these drives.

For this system, I would put the paging file on a regular hard drive, to avoid the wear factor.  It won't bring down performance much.
pgm554

XP  and Vista are not W7.

W7 has been tweaked with trim support for SSD's, resulting in better read and write response times for SSD's.

In fact,this article says if you got 4gb of RAM,just disable the swap all together.

http://www.bit-tech.net/hardware/storage/2009/08/27/ssd-performance-tweaks-for-vista/1
Callandor

>For this system, I would put the paging file on a regular hard drive, to avoid the wear factor.  It won't bring down performance much.

I just realized this is a laptop with only one drive, so ignore this.
Experts Exchange has (a) saved my job multiple times, (b) saved me hours, days, and even weeks of work, and often (c) makes me look like a superhero! This place is MAGIC!
Walt Forbes
xema

Callandor;
When I said "behave as a normal HD", I meant the structure and the process to write and read files, I'm aware they are sustancially faster, but also I've read they have a bigger "wear factor" than Normal, mechanical, HD.
Callandor

xema, thanks for the clarification.
StuWhitby

Set the page file size to 0, get hold of Process Explorer from http://technet.microsoft.com/sysinternals and watch your system commit history.  If this is has a nice consistent gap at the top then you don't strictly require a page file.... but it might be a good idea to launch PE at boot time and set that graph to show in your notification area (Options/Tray icons).  If this stays under about 80% (guessing) without a page file when you're running a fairly high (but not unreasonable) workload, then you don't need a page file from a memory management side.

Leaves you stuffed for finding out what happened in the event of a crash, though if you set it to hold on a bluescreen rather than reboot (can't remember where to set that, but I'm fairly sure the option exists), I find that a digital camera image of the screen is handy to try to track down what happened after it's back up.
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
John

Thank you, and I was pleased to assist. .... Thinkpads_User