Specialty Forums
Security and Virus
General Hardware
CPUs/Overclocking
Networking
Digital Photo/Video
Office Software
PC Gaming
Console Gaming
Programming
Database
Web Development
Digital Home

General Forums
Windows XP
Windows Vista
Windows 95/98
Windows Me
Windows NT
Windows 2000
Win Server 2008
Win Server 2003
Windows 3.1
Linux
PDAs
BeOS
Novell Netware
OpenVMS
Solaris
Disk Op. System
Unix
Mac
OS/2

Drivers
Driver Scan
Driver Forum

Software
Automatic Updates

BIOS Updates

My Computing.Net

Solution Center

Free IT eBook

Howtos

Site Search

Message Find

RSS Feeds

Install Guides

Data Recovery

About

Home
Reply to Message Icon Go to Main Page Icon

Subject: Should we set Virtual Memory?

Original Message
Name: EK
Date: September 7, 2001 at 08:42:42 Pacific
Subject: Should we set Virtual Memory?
Comment:
Recently I ran SiSoft SANDRA to test my system, one of the interesting suggestion from the software is to "Use a fixed-size swap file. This is faster than variable-size swap file." (Tip T2005)

Is it true? If so what size should I set for the virtual Memory?

Thanks in advance!

EK


Report Offensive Message For Removal

Response Number 1
Name: Eric
Date: September 7, 2001 at 08:52:49 Pacific
Subject: Should we set Virtual Memory?
Reply: (edit)
It depends on how much memory you have but 2 to 2 1/2 times your system memory seems about right. Then, you can use a utility like Norton to move the swap file to the beginning of the drive.

Report Offensive Follow Up For Removal

Response Number 2
Name: jFrOg
Date: September 7, 2001 at 08:58:49 Pacific
Subject: Should we set Virtual Memory?
Reply: (edit)

I could be wrong, but if memory serves me correctly that after you fix the VM settings and then run a defrag, it will automatically place it in the front of the drive. I personally steer away from any of the Norton/McAffee Utility progs because they seem to cause more problems than they fix. And as far as size goes I set the minimum to 2 times the ram and the max to 2 1/2 times the ram.
 
H
opeThisHelps,
 
-me-



Report Offensive Follow Up For Removal

Response Number 3
Name: DaBeast
Date: September 7, 2001 at 10:13:00 Pacific
Subject: Should we set Virtual Memory?
Reply: (edit)
jFrOg,

I'm not sure that you get the most benefit from using a difference in the two settings. This would still require windows to do a calculation to determine required size and I'm not sure if it would set it aside as a block because it does not know that the current size won't change. (If it sets aside the maximum size anyway, why use a smaller minimum setting?)

Just a thought. I really don't know for sure.

I think I've told you before, but, cool frog.


Report Offensive Follow Up For Removal

Response Number 4
Name: jFrOg
Date: September 7, 2001 at 10:23:14 Pacific
Subject: Should we set Virtual Memory?
Reply: (edit)

Thinking about it, I think you are right about that. I will have to make some adjustments.
 Thanx for the compliment.
 
-me-
 
 



Report Offensive Follow Up For Removal

Response Number 5
Name: Miroslav Vadovic
Date: September 7, 2001 at 10:48:58 Pacific
Subject: Should we set Virtual Memory?
Reply: (edit)
the fixed size swap file has two benefits
- the cpu does not have constantly to recalculate the size of the swap file from the free space on your hd
- if min=max then the swap file will not get fragmented(it takes much more time to access a diferent location on the harddrive than just continue reading/writing to the same location)
...regardless of amount of physical RAM you probably dont need more than 200 meg swap file... the rule of thumb 2.5 x physical memory was valied for small amounts of RAM couple years ago... it is easy to monitor how big the swap file gets for couple days and then round it reasonably higher and set the min and the max to the same value.... also your first partition might not be the fastest... i checked on pcpitstop my first partition with swap file on it and then my second partition with swap file on the second one... my second partition is faster because it is not fragmented at all and does not get fragmented even with the fixed swap file on it.. the fist partition has still some scathered system files around it that cant be moved easily... i would not use any nortons or mcafees to mess the swap file up
The speed difference is anyhow not noticable... the only things that are noticable are much less hard drive thrashing and much faster defrag
Regards


Report Offensive Follow Up For Removal

Response Number 6
Name: guru
Date: September 7, 2001 at 14:46:20 Pacific
Subject: Should we set Virtual Memory?
Reply: (edit)
aaah sh##t, i gotta agree with miro, as much as it goes against the grain(lol). except for nortons utilities. those are ok if you do a custom install and use only windoctor,diskdoctor, speeddisk,optimizer and
registry editor. anything else from nortons i leave right alone.

Report Offensive Follow Up For Removal

Response Number 7
Name: Renaissance Man
Date: September 7, 2001 at 17:56:37 Pacific
Subject: Should we set Virtual Memory?
Reply: (edit)
Set min/max figures to 2 times your ram. Both should be the same to avoid resizing.

NOT all defragmenters put the swap file at the beginning of the disk--where it belongs. Norton and MacAfee do.

For the most thorough discussion of swap files you will ever need or can imagine, go to www.rojakpot.com and look in the "Speed Demonz' Area."


Report Offensive Follow Up For Removal

Response Number 8
Name: EK
Date: September 7, 2001 at 23:19:06 Pacific
Subject: Should we set Virtual Memory?
Reply: (edit)
Dear all,

Thanks for all your advices. Your very useful inputs are greatly appreciated :)

EK



Report Offensive Follow Up For Removal



Use following form to reply to current message:

   Name: From My Computing.Net Settings
 E-Mail: From My Computing.Net Settings

Subject: Should we set Virtual Memory?

Comments:

 
  Homepage URL (*): 
Homepage Title (*): 
         Image URL: 
 


Data Recovery Software



Version Tracker Pro
Keep your software current and secure, effortlessly

Click Here for a Free Scan

Driver Agent
Automatically find the latest drivers for your computer.
Click Here for a Free Scan



The information on Computing.Net is the opinions of its users. Such opinions may not be accurate and they are to be used at your own risk. Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE

All content ©1996-2007 Computing.Net, LLC