Virtual Memory Setting

Hi,

Relax, you're in the right place. This is kinda L O N G. As a guy where I worked, before I retired, used to say of me ... "Ask Jimmy what time it is and he'll tell you how to build a watch" ;^)...

As concerns memory and speed, the addition of memory does not necessarily guarantee a performance boost. Memory usage is task dependent and when tasks performed don't require additional memory, no performance benefit will be realized. If you really would like to experience a performance boost, then your upgrade path should take the direction of a faster processor and/or faster hard drive. If you were to do both, you would undoubtedly experience a significant increase in performance. Now to the task at hand. Sit back ... relax ... the lecture is about to commence...

Windows 98 does a much better job of managing virtual memory (the swapfile) than did Windows 95.  Nonetheless, you can still reap some benefit by managing things yourself.  Start of Lecture ... A hard drive is much slower than memory.  The hard disk serves as an extension of physical memory as virtual memory, also commonly referred to as the paging file or swapfile.  The swapfile grows and shrinks as needed, but this activity entails CPU cycles, and prevents your hard drive from performing any other tasks until the resizing activity is completed.  As the swapfile grows, it can become fragmented across your hard disk.  The extra "housekeeping" required to monitor and manage the swapfile's size and fragments can cause Windows to become sluggish.  The concept of a fixed (same minimum and maximum size), permanent swapfile arose from the notion that a swapfile of a fixed size would not have to be managed (constantly resized) by Windows (a good thing) and would remain unfragmented (also a good thing).  The flaw in the reasoning, however, becomes apparent the first time that more virtual memory is required than accounted for by the size of the permanent swapfile.  The result is an out of memory condition (error).  The objective should be to establish an unfragmented swapfile of a suitable size.  With an unfragmented swapfile, Windows can spend its time using the swapfile instead of managing it.  You'll read various theories concerning how to set up the swapfile.  One popular notion is to make it a fixed size, 2.5 times the size of your physical memory for both the minimum and maximum size.  The factor (multiplier) of 2.5 is flawed because the addition of physical memory diminishes the requirement for virtual memory.  There's an inverse correlation at work here.  Are you with me so far?  Good.  I prefer to share in the responsibility of virtual memory management, establishing what might be called a "semi-permanent" swapfile.  What do I mean?  Well, follow along.  In Control Panel|System|Performance|Virtual Memory, you are afforded the opportunity to allow Windows to manage the swapfile or you can elect to manage it yourself.  I chose to "Let me specify my own virtual memory settings".  I set the minimum value, but let Windows determine the maximum value based on available hard disk space.  Windows will issue a warning message.  Just ignore it.  The next time you bootup, Windows may adjust (reset) the maximum value depeniding upon your entered minimum value.  By all means, do a defrag so that your swapfile will be comprised of contiguous space (no fragmentation).  You will likely note that your Win386.swp is now in two places.  It was initially in the Windows folder, but now also appears in the Root directory (C:\).  For some reason, when you elect to manage virtual memory yourself, Windows relocates the swapfile.  It is safe to delete the Win386.swp in the Windows folder.  Now about that minimum size.  Your usage generally dictates what the target value should be set at, and "everyone's mileage may vary".  When I had 128MB, I set the minimum at 250MB.  When I went to 256MB, I reset it to 150MB.  When I went to 512MB, I again reset it to 100MB.  The objective is to establish a virtual memory (swapfile) value that is generous enough so that your swapfile isn't resized and/or fragmented by Windows.  To this end, check your Win386.swp now and then.  If set too low, it will increase in size.  If set too high, it will never increase in size.  With a bit of experimentation, you will eventually home in on an appropriate value.  Verify that your C:\Windows\system.ini file has the following entry in the [386Enh] section ... PagingDrive=C:  In the unlikely event that it is not present, then add it so Windows "knows" where to "look" for your swapfile.  The system.ini should have the entry MinPagingFileSize=N ("N" being the the value in bytes that you entered as the minimum swapfile value).  Of utmost importance is the addition of the following entry in the system.ini ... ConservativeSwapfileUsage=1.  This entry will ensure that your physical memory is used before your virtual memory (swapfile) is used.  Now that you have a working knowledge of the swapfile, why not put it to work?  I know, I know ... probably more than you needed to know or asked for, but I didn't want to overlook anything.  That's just me.

Jim McNamara

Message Edited by jimmymac_4 on 03-12-2003 12:55 PM

And if you remove or remark the PagingDrive=C: entry in System.ini [386Enh] section and reboot, Windows will use the swapfile in Windows folder again.

 

Message Edited by esquire on 12-15-2002 12:05 PM

Jim:

Thanks so much for your detailed explanation of virtual memory settings — I for one appreciate the time you took to explain it so that it is understandable to a neophyte such as I. Perhaps you could help me this situation: I have two hard drives on my Dell Precision 220 Workstation. Windows ME is on the C Drive and Windows XP is on the D Drive. I have not yet encountered a problem regarding memory or low resources with Windows XP; however, it does happen often enough with Windows ME to prompt me to seek a solution. I have 512MB of RAM and a Pentium III processor. Would these same settings apply to a dual-drive/dual-operating system situation? I am particularly concerned with the "PagingDrive=C" setting. Any tips or pointers you or anyone else might have will be greatly appreciated.

Cats

 

Hi,

Hopefully, one of the XP experts that frequent this Win98 forum will be able to address your XP concerns, but this much I can tell you.  In XP, you will not experience the resource limitaions that you are experiencing with ME.  System resources are employed to ensure backward compatibility for 16-bit programs originally written for DOS and Windows 3.x.   Do not make the mistake of confusing memory and system resources.  The amount of memory that is allocated for system resources is pre-determined by the operating system.  For Win95/98/ME, that limit is 64KB.  You cannot increase this limit by adding memory.  To learn more about system resources, go here...

www.aumha.org/a/resource.htm

Jim McNamara

Thanks a ton so far Jimmymac,

I understand what you're saying but have a question: First you say this:

In control panel>system>performance>virtual memory, you are afforded the opportunity to allow Windows to manage the swapfile or you can elect to mange it yourself. I chose to "Let me specify my own virtual memory settings" and set the minimum, but no maximum value (Fair enough)

Then later you say:

Your usage generally dictates what the target value should be set at, and "everyone's mileage may vary" When I had 128 MB, I set the minimum at 250MB. When I went to 256mb I reset it to 150mb. When I went to 512MB, I again reset it to 100MB.

I assume the 2nd quote is stating what the value you're setting in the first quote right? Ok, if so, then how do I enter 100MB (I have 512mb ram)? Do I just enterthe number 100 because it knows it's in mb's? Or what does the actual number of 100mb look like that I will enter as my minimum? I know you said leave the MAX blank. (Which I'll do)

The number I have in there currently is 1024 which someone told me to put in once a while back. But from what I'm reading here it sounds like the number in there is actually kbs, which would make my 1024 be totally wrong.

Can you tell me, if I should be trying 100mb like you said, what that would look like? Or do I need to convert 100 to kbs or leave it as 100 or do I even need to convert 100 to bytes?

And thanks again Jimmymac. I'll hang up and listen to your answer.

Message Edited by Shafes on 02-22-2003 09:19 AM

Hi,

In answer to your questions...

1. Right, the 2nd quote refers to the value set in the 1st quote.

2. Yes, the number entered is assumed to be in megabytes, so for 100 megabytes, simply enter 100 (without the MB).

3. You're right.  Your current setting (1024) is totally wrong.

4. No KB to MB conversion is required.  Like I mentioned in #2 above, the number is in megabytes and should be entered as such.

Sorry it took this long to get back to you.  I've had a busy stretch that curtailed my available PC time.  I hope that I have addressed all of you concerns to your satisfaction.

Jim McNamara

Message Edited by jimmymac_4 on 02-24-2003 03:23 PM

Wow that's wild. Using Win98SE and just tried adjusting the min to 100 and leaving the max blank.

Win98SE won't let me set a value for the MAX that is blank, zero or anything <100 and still be able to click OK. Guess I have to set the MAX for 100 too? I can at least click OK (It lets me) if I choose anything >= 100.

 

Thanks again.

 

Hi,

As detailed as my  L O N G  explanation about all this was, perhaps I should have been a bit more clear about this particular issue.  Do not set your maximum to 100.  Although it is highly unlikely that with 512MB of physical memory and 100MB of virtual memory that this will ever occur, but should you exceed the total capacity of your allocated memory (512 + 100), you will experience an "out of memory" condition".  What you need to do is to just set the minimum value, but enter nothing for the maximum value.  Windows will take care of that for you based on available hard disk space.  This is what I call splitting the difference with Windows ... you set the minimum value and Windows sets maximum value.  In effect you and Windows share the responsibility for virtual memory management.  Understand now?

Jim McNamara

P.S.  I think I will edit my original post to add the clarification.

 

Message Edited by jimmymac_4 on 02-11-2004 11:07 PM

Message Edited by jimmymac_4 on 02-11-2004 11:12 PM

Actually I totally understood you the first time. I said I entered 100 as the MIN and tried leaving the MAX blank, and if I leave it blank, it won't let me choose OK to close it out. I have to at least enter 100 as the MAX if I want to be able to click OK. If I set the MIN at 100, I can't set the MAX at anything less than 100 and I can't just leave it blank and still be able to click OK and exit. Win98SE will not let me.

Sorry, it appears I should have made myself more clear. Thanks again.

 

Oh and the place I got the idea for changing my numbers to 1024 for both was from Speedguide.net. They have alot of good tweaks there.

Here's the link: It's in the first section entitled Virtual Memory Settings:

http://www.speedguide.net/Windows/win_perform.shtml

Message Edited by Shafes on 02-24-2003 07:31 PM

Hi,

I'm not convinced that you really do completely understand what I've been saying, so I will give this one more try.  There should have been a number already in the Maximum value and it should corresond to the Hard Disk (free) value.  You should not attempt to reset this Maximum value to blank or anything number that matter.  Allow me to reiterate ... you should set the Minimum value and allow Windows to set the Maximum value.  This is what I meant by sharing the virtual memory management responsibilities.  The crux of the problem is that you attempted set the Maximum value.  Please re-read my prior posts.  For what it is worth, the reason why you were unable to set the Maximum value to anything less than 100 is becuase Windows won't let you set the Maximum to less than the Minimum for obvious reasons.  A Minimum value cannot not exceed the Maximum value, and conversely a Maximum value cannot be less than the Minimum value.  Now with that said, if you are still experiencing difficulties, do this:

1. Click first on the radio button "Let me specify my own virtual memory settings", and then, click on the raido button "Let Windows manage my virtual memory settings".  Your values should now read Minimum=0, Maximum=No maximum.

2. Click on the radio button "Let me specify my own virtual memory settings", again.  The Hard disk and Maximum entries should be the same and the Minimum value should be "0".

3. Now, change ONLY the Minimum value to 100.  DO NOT change the Maximum value.  Click the OK button bar and click "YES" in response to the prompt.  Now, go back an have another look at your virtual memory settings and you will note that the Minimum and Maximum values are greyed out but are as intended (Minimun = 100 and Maximum = No maximum).  In addition, you will note that Windows is aware that it is managing the Maximum setting and has reset the radio button back to "Let Windows manage my virtual memory settings".

I hope this clarifies things for you.  If not, it is not from lack of trying.  By the way, I am quite familiar with Speed Guide.  I bookmarked (saved as a favorite) the website years ago.  Whereas this is an excellent site, the advice provided, upon which you based your previous virtual memory setting ... "Make the swap file twice the amount of RAM you have on your system ( or at least the same size as your RAM ), ... is not good advice for the reason previously stated.  Plain and simple, there is an inverse correlation at work here.  As physical memory is increased, the need for virtual is correspondingly decreased.  Consequently, any numerical formula such as Speed Guide's (2 times, or at least the same size as your RAM) is both misleading and frankly, incorrect.

Jim McNamara

Message Edited by jimmymac_4 on 02-27-2003 12:01 PM

Hi Jim,

I've been following along here because I messed with my Virtual Memory about 2 years ago, and now I have a question.

I have swapfiles in both locations. According to your directions, it is OK to delete the swapfile from the C:\Windows folder. Yet when I just now looked at mine it says that it contains 16,384 KB and was last modified on 02.13.03. Meanwhile the swapfile in the C:root directory contains 98,304KB and was last modified on 02.26.03, today.

I believe that the 16,384KB file may have been following me around for the past two years, and that the most-recent modification may somehow relate to something irrelevant e.g. a system restoration, on February 13 of this year (if I did something like that then). Would this be logical? And...should I just delete the 16,384KB file and be done with it?

Also, you wrote:

"Of utmost importance is the addition of the following entry ... ConservativeSwapfileUsage=1. This entry will ensure that your physical memory is used before your virtual memory (swapfile) is used."

When I went into my msconfig and checked the System.ini tab, I found all of your above-mentioned items in the [386Enh], with the exception of the ConservativeSwapfileUsage=1 . Is it your direction that I should click on an empty space under the [386Enh] and select New and type in ConservativeSwapfileUsage=1?

As I previously said, two years ago I messed with my Virtual settings. They are currently set as follows:

• My minimum is set for 96
• My maximum is No Maximum
• My hard disc is C:\2102MB free
• Windows is marked to currently manage my virtual memory settings.

I believe that I set the minimum at 96 two years ago based on something that I read somewhere, and then...that I got very confused during the process because Windows did not appear to allow me to make any adjustments.

Now, after reading your above-explanation of things, I believe that I understand what may have gone wrong in my first attempt.

It appears to me that I can make things better for myself if I enter the expression ConservativeSwapfileUsage=1 in the correct place, as well as delete the C:\Windows file. Am I correct in these two assumptions?

I agree w/David Greg on the system.ini tweak "ConservativeSwapfile"  

Do that,, forget the virtural memory tweaks, little to no benefit in 98, 95 yes.

Also, right click on My Computer, goto performance, change typical role from Desktop Computer to "Network Server" this increases read-ahead optimization.

BTW, the Conservative Swapfile demands a minimum of 128mb suggested more, like 256-512mb RAM

For real speed increases, get a modern HD with dense clusters, 7200rpm and 8mb of cache. Like the WD Special Edition series, Dell has some here->>

http://accessories.us.dell.com/sna/ProductDetail.aspx?category_id=863&keyword=&mnf=&prst=&prEnd=&sku=A0069941&mnfsku=&SearchType=&Page=productlisting.aspx&spagenum=1&Pageb4Search=&InStock=&items_per_page=25&orderby=&image_flag=True&refurbished=&c=us&l=en&cs=19&iCompatid=

Everyone else has had a word - so here is my 2cnts worth (as a limie it should be 2p)

You not only need to know the current ram but the use that the computer is being put to. If using for photos or video manipulation you should setup a swop file as large as possible as very often progs doing scanning with large DPI can very fast use up the available RAM & swop file such that windows needs in mid scan to increase the swop file causing a lockup. Back in Win 3.1 days we would set up a permanent swop file (as large as possible) because of this need.

Hope I haven't confused the issue. But usage of the machine is as important as the hardware.

Hi David,

I'll do my best to answer your questions by the numbers:

1.  Right-click on each of your swapfiles and click on properties.  Check the file dates and I am quite sure that you will find that your "active" swapfile is the one designated in the virtual memory properties dialog box in "Hard disk:".  Verify this and go ahead and delete the one in the "inactive" swapfile, most likey the one in your Windows folder.

2.  You are correct in your assumption concerning how to add the ConservativeSwapfileUsage=1.  You can proceed as you indicated (few people seem to even be aware of your method) or you can simply edit you system.ini with your editor of choice to get the job done.  While you are at it, beneath the [386Enh]  bracketed heading, look for a line that reads PagingDrive=C: (the drive letter and location may differ on your particular system (e.g. PagingDrive=D: or PagingDrive=C:\Windows).  From what you said though, it would seem that you already have this entry.  If so, this is another means of verifying which of the two is your "active" swapfile.  If you don't have this entry, add it on a separate line.  This is how you specify where your swapfile (virtual memory) is to reside.  Assuming that your "active" swapfile is in your root directory, then this entry should read PagingDrive=C:

3.  Since I don't know your physical memory size or you typical computer use, I will refrain from commenting about your minimum setting of 96.

4.  As concerns your assumptions ... deleting the "inactive" swapfile won't merit you a performance gain, but doing so will free up some much needed disk space since you are getting a bit cramped in that area (2102MB free).  The ConservativeSwapfileUsage=1 might reap a performance benefit, depending upon how you use your PC.  By all means, give that one a try.

Hope this helps,

Jim McNamara

I've recently been getting a lot of error messages regarding lack of memory. I was poking around the System stuff, and found the Virtual Memory thing. I'm running Windows 98, Pentium III, with 384 MB of RAM, and two hard drives, one 20 Gig and one 30 Gig. Will it be alright for me to set the minimum down to 100? Will that help any? When I click the "Let Me Specify" thing, it sets the Max to 8534. I feel like I shouldn't be having this much memory problems with this system. If anyone wants to jump in with any comments, feel free. Thanks in advance!