Increasing Your Virtual Memory

[Hackr]

This makes your computer faster by utilizing your HD space as virtual RAM. ( Takes around a gigabyte of space,when initialized. but still speeds up your computer greatly!)
I do not recommend doing this if your hard drive space is less than 20gb.

Alright, this is how you do it:


Instructions:
1. Hold down the Windows Key and press the Pause/Break button at the top right of your keyboard (another way is right-clicking your computer and clicking Properties).
2. Click on the Advanced tab.
3. Under Performance, click Settings.
4. Then click the Advanced tab on the button that pops up.
5. Under Virtual Memory at the bottom, click Change.
6. Click the Custom Size button.
7. For the initial size (depending on your HD space), type in anywhere from 1000-1500 (although i use 4000), and for the Maximum size type in anywhere from 2000-2500 (although i use 6000).
8. Click Set, and then exit out of all of the windows.
9. Finally, restart your computer.
10. You now have a faster computer and 1-2gb of virtual RAM!


but sometimes it doesnt work ok :(

[Novindu]

hehe... i kno dis...... but wont work as fast as u say man...........

[chip]

yeah this thing works but it'll get ur pc in some troubles ryte?:confused:

[Anusha]

Do no use different values for initial size and maximum size. The recommened thing to do is to have the initial value as well as the maximum value the same, where maximum value is calculated by multiplying total physical memory by 1.5. The logic here is to undo the chances of fragmenting the pagefile, when you increase it only when necessary. If it can't find free space right after the end of the existing pagefile, it will get fragmented and will suffer a performance hit.

However, if you are still running on 128MB RAM, you will need a very big pagefile.

But if you have 1.5GB or better yet, 2GB of RAM, do not use the pagefile because it will not give you the performance you would have expected by adding that extra RAM as Windows will still use the pagefile even if you have 1.5GB of RAM left without being used. It's not efficient at all.

[chip]

Do no use different values for initial size and maximum size. The recommened thing to do is to have the initial value as well as the maximum value the same, where maximum value is calculated by multiplying total physical memory by 1.5. The logic here is to undo the chances of fragmenting the pagefile, when you increase it only when necessary. If it can't find free space right after the end of the existing pagefile, it will get fragmented and will suffer a performance hit.

However, if you are still running on 128MB RAM, you will need a very big pagefile.

But if you have 1.5GB or better yet, 2GB of RAM, do not use the pagefile because it will not give you the performance you would have expected by adding that extra RAM as Windows will still use the pagefile even if you have 1.5GB of RAM left without being used. It's not efficient at all.

thanx 4 da info.. thanx alot:D

[azaamDAsquad]

thanks fer d info...

[Anusha]

No problem.

[sheyan]

ok thanz machoo.

[zerocool]

Do no use different values for initial size and maximum size. The recommened thing to do is to have the initial value as well as the maximum value the same, where maximum value is calculated by multiplying total physical memory by 1.5. The logic here is to undo the chances of fragmenting the pagefile, when you increase it only when necessary. If it can't find free space right after the end of the existing pagefile, it will get fragmented and will suffer a performance hit.

However, if you are still running on 128MB RAM, you will need a very big pagefile.

But if you have 1.5GB or better yet, 2GB of RAM, do not use the pagefile because it will not give you the performance you would have expected by adding that extra RAM as Windows will still use the pagefile even if you have 1.5GB of RAM left without being used. It's not efficient at all.


Very True! ;)

First of all i do not recomend using custom settings, just let windows manage it.

There is another thing you must consider when using virtual memory. Normally you have more than 1 drive ne, if you are going to use custom settings for virtual memory you can split it into all the drives. That way when system is reading a file from a drive it will page in the related drive.

ex: when the system is reading a file from D: it will store in the page file in D: and when the system is reading a file from C: it will sore in the page file in C:

The logic here is same as the above, system will not have to move between sectors so far when read and write. So it will get bit faster.

But you dont see that much of a effect so no point of using that. ;)

[Anusha]

Why would system have to page a "file" when it is being read?

Why it is a good thing to spread the pagefile among more drives (don't, i repeat, don't spread it along partitions on the same disk - one drive should have one pagefile) is because then the paging can be improved the same way how RAID 0 improves disk read/write performance. It can then read/write pages simultaneously (well, it's not 100% simultaneously because the drives are not identical and even it they were identical, the pagefile wouldn't be residing at the same location on the disks - but you get the idea right?)

When you have pagefiles on more than one disk, paging will happen on all the pagefiles. It's not that only one pagefile is active at a given time. Both are active!!!

[zerocool]

Not true! :eek: :eek:

Contact Microsoft and see for your self. That information was not made up by me. That is something i have learned from microsoft (when i was doing my MCSE). It is in the text books man!

[rapa]

hehe... i kno dis...... but wont work as fast as u say man...........

Hmmmmmmm :( :yes: :yes: :yes:

[zerocool]

Hmmmmmmm :( :yes: :yes: :yes:

Agreed :yes: :yes: :yes:

[Anusha]

I'm not wrong (only half right). But you are wrong, zerocool.

When you split the pagefile, it acts differently according to the situation.

1st situation:

When one drive, which a pagefile resides on, is busy, the VMM (Virtual Memory Manager) uses the pagefile segment on the least busy drive. For example if you have two pagefiles in C: and D: and if you are loading a program from C:, the pagefile of D: will be used.

2nd situation
When either of them are not busy (or both are busy), simultaneous operations are performed on the multiple pagefiles (http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/sag_mpmonperf_15.mspx?mfr=true)
You can't say I'm wrong, because Microsoft says so :D

According to that article, if you have a fast drive and a slow drive, it is better to have the pagefile only on the fast drive.

[zerocool]

Ok what you said gonna happen some times.

Anyway my point is this. If we have more drives you can connect them in seperate IDE cables (one in primary and the other in secondary). That way system can access the page files simultaneously. There is no point if your hard drives in the same IDE cable. Anyway this will not gaonna boost your pc this is just a slight performance hit. ;)

[Anusha]

Yeah
I have to agree with your last post, zerocool. When the drives are in the same IDE channel, one has to be Master and the one has to be Slave. What I have heard is that the Master is given the pirority. The slave is only allowed the transfer data when the channel is idle. So the I/O operations on the slave drives will be slow, if the master drives are doing I/O operations.
This is the same reason why people ask to avoid RAID setups on the same IDE channel. I'm not sure whether or not it will slow down the RAID setup and if yes, by how much. But for optimal performance you need to have them on seperate channels.

Hey zerocool, don't be offended by what I said. We are cool, right?

[zerocool]

Yeah
I have to agree with your last post, zerocool. When the drives are in the same IDE channel, one has to be Master and the one has to be Slave. What I have heard is that the Master is given the pirority. The slave is only allowed the transfer data when the channel is idle. So the I/O operations on the slave drives will be slow, if the master drives are doing I/O operations.
This is the same reason why people ask to avoid RAID setups on the same IDE channel. I'm not sure whether or not it will slow down the RAID setup and if yes, by how much. But for optimal performance you need to have them on seperate channels.

Hey zerocool, don't be offended by what I said. We are cool, right?


No Man im cool :cool: (actually im zero cool :lol: ) That's what a community is we have to share our opinions. ;)

[neshe]

thanks 4 da tips

[amila325]

wow gr8 info here thanks every body