my home PC is running XP Pro with 4GB RAM: with that amount of real RAM I'd say that virtual RAM is not necessary hence I've disabled the pagefile). In my opinion the only correct pagefile settings for a Windows host now are either: leave it on defaults, or disable it altogether (the latter only if your PC is way overspecced with RAM, e.g. Mpack wrote:All except the first are standard tips related to how to get the best possible performance out of your PC, but the tips are quite old (Win98 era) and I doubt they are of much value with XP and later. Seems to have worked out pretty well for me over the years, hope that helps you out. since my vm's dont have much ram associated to each and will eventually use the page file, i set the page file to a static amount, then download and run pagedefrag, just to eliminate any fragmentation in the vm's page file. i usually make the number smaller than what that comes out to, so i don't totally use up all the RAM on my host machine. Then that gives you a rough idea of how much you can allot to each virtual machine. What I do is depending on how much available RAM i have on my host machine after its booted and all of its normal stuff is running, is to take that available amount of RAM (not total ram in the computer, but what's not in use) and divide that by the number of VMs i'm going to run at the same time. it does have its advantages when you're talking physical disks, but not sure with virtual disks since all your virtual disks are probably running off the same physical hard drive in your host machine anyway. all the paging can be separated out and done on the secondary drive, whereas your main drive will be for everything else. and the idea behind having it on its own physical disk is to improve performance. you can increase it to a bigger multiple, but doesn't sound like you need or would want to based on what you're doing.īy default the page file is going to be "very large" so don't worry about that. ![]() You'll notice on at least XP machines the "recommended" value it tells you is usually 1.5 times what you have, its been that way for a long time as a standard. The page file is still a file mind you, so if its not set to a static size and is allowed to grow as needed, it will become fragmented. The first tip I'm not sure about, I could see where you wouldn't want a virtual machine using a page file on a host that's using a page file because if both host and guest(s) are using the page file (because you don't have enough ram in the host machine to begin with), that would be real performance heavy on your hard drive and slow everything down. Perhaps someone can just direct me to a good discussion on seems that there should have been one.I just can't seem to find it anywhere. My main goal is to have good performance even though my host machine has just 3GB or RAM. I am not gaming or anything, so my needs are simple, hence my thought that there would be a base configuration to start with that the VirtualBox developers think is optimal. My goal is just to have a few basic XP-Pro SP3 guests, probably only two running simultaneously at most. ![]() I cannot seem to find an "official" suggestions on what configuration to start with for my guestOS setups. A fourth says leave it at the defaults, which would be a variable sized page file on the virtual c drive. A third says it needs to be very large, but on a separate disk. ![]() Another suggests that it should be fixed in size (beginning and end size set the same) so the page file size is 1.5 or 2 times the RAM, but never changes in size. virtual memory on xp (paging file) should be completely disabled when running a VM (that was a VMWare suggestion, not a VirtualBox one).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |