PDA

View Full Version : vm size, virtual memory



random
January 17th, 2004, 12:21 AM
wut is virtual memory and how does it affect ur cpu usuage?

THEDOGGG
January 17th, 2004, 02:01 AM
wut is virtual memory and how does it affect ur cpu usuage?

Virtual memory is when windows uses a portion of the hard disk as additional ram, this is called a page file. Generally the more ram you have, the less virtual memory your computer needs to run programs, making your computer faster because it doesn't have to access the hard disk. It is best to set a static page file size about 2x the size of your ram (ie. if you have 256mb of ram set it to 512). To do this go to your control panel (XP), click settings, performance and maintenance, system, advanced. Under performance click settings, advanced.In the bottom where it says virtual memory click change. Click custom size and type in the same value in inital and maximum,(ie. 512 in the previous example). Click set, ok. If it asks you to restart the computer click yes.

random
January 17th, 2004, 06:51 PM
which would cause more cpu usuage, a bigger mem usuage program or a bigger virtual memory size program?

isus
January 17th, 2004, 07:06 PM
cpu usage with virtual memory is a non-issue for any cpu over 100mhz.

when part of the ram is paged out to pagefile/virtual memory, it causes the cpu to use a few cycles because it has to write the request to the hard drive and what not so that the memory is actually put on the hd.

cpu usage really doesn't matter. what does matter is speed. when something is paged off, instead of using the 2.1gb/s bandwidth for memory, you need to page it off on a .1gb/s ata cable. (these are just low end. if you have pc3200, than you move at 3.2gb/s, sata moves things at 150mb/s, or .15gb/s)

and the 2x rule doesn't work...

guidelines from ms is 1.5x, but even that is overkill... nearly a gig of wasted space for 512mb ram. i would use:
128mb ram, 128mb pagefile
256mb ram, 256mb pagefile
512mb ram, 256mb pagefile
1gb ram, turn pagefile off.

Malicious Intent
January 17th, 2004, 07:17 PM
Mine was on 768. It is now on 256 (512mb RAM). Thanks Isus and THEDOGGG.
However, I can't help but think that since I have 35GB free harddrive space, I may have as well kept it at 768?

isus
January 17th, 2004, 09:03 PM
well, here's my opinion on this, take it for what it's worth...

the bigger the pagefile, the more continuous free space windows need free on your hard drive... when you open up disk defragmenter in winxp, and press analyze, that big green chink is your pagefile.

the smaller it is, the better chance you have of getting it towards the left side of the analyze graph. this means the pagefile is closer to the inside of the hard drive.

supposedly, being closer to the inside of the drive lets the drive work with that file faster... for example, if your keyboard was 6 feet away from you, it would take you time to get to it. but if it was right in front of you, you can just start typing, right?

same way for a hard drive. so a smaller page file helps it fit where it can. also, why use up 512mb gard drive space (768-256)? that's almost part 1 of 2 of a movie ;)

for the most part, the only way to gain performance through a change of the pagefile is to turn it off. but that is only good for computers with 1gb ram or more.

DainBramaged
January 17th, 2004, 09:44 PM
Most commonly, the pagefile is set to 1.5x the amount of physical memory, RAM, you have. But, as isus has pointed out, it really doesn't make much sense unless you are working with an application that uses large amounts of resources that aren't always needed right away.

More recently, I have set my pagefile equal to the amount of RAM I have (512).

phalkon30
January 17th, 2004, 10:38 PM
When I installed windows a few months ago, I made a 2 gig partition on the front of the drive, then made the rest of the drive my windows partition. My page file went on the 2 gig drive, along with my temp internet files, and temp cd burning files.

I couldn't believe how much faster windows ran. Nearly all the fragmentation stays on one drive, and since its all physicly on the front of the drive, it doesn't have to search around a big partition in the middle, so has much better access times.

isus
January 17th, 2004, 11:31 PM
When I installed windows a few months ago, I made a 2 gig partition on the front of the drive, then made the rest of the drive my windows partition. My page file went on the 2 gig drive, along with my temp internet files, and temp cd burning files.

I couldn't believe how much faster windows ran. Nearly all the fragmentation stays on one drive, and since its all physicly on the front of the drive, it doesn't have to search around a big partition in the middle, so has much better access times.
this is a good way to partition. however, if i was doing it, i would make a 3rd partition, after what is your first, of perhaps 3gb and put my windows folder on that. after that, i would create a 4th with my programs. the last, and furthest out would be my documents... who really needs high read/write speeds when opening an mp3 or word document?

DainBramaged
January 18th, 2004, 12:31 AM
this is a good way to partition. however, if i was doing it, i would make a 3rd partition, after what is your first, of perhaps 3gb and put my windows folder on that. after that, i would create a 4th with my programs. the last, and furthest out would be my documents... who really needs high read/write speeds when opening an mp3 or word document?
I suppose if you have like a bajillion mp3s, it might get a little pokey loading them all up in Winamp ;-)

phalkon30
January 18th, 2004, 09:51 AM
Well isus, I've also got a 160 gig seagate with my documents on it. They stay fast, and if I'm reorganizing stuff, it won't effect windows performance because its on a different drive.

Not to mention, when I reinstall windows, all my documents are on a separate drive, no need to back them up.