running visual studio and sites inside VMware inside RAM Disk

Question

hi, i am seeking advise on this one. i have a machine with 24 GB so i was planning to install Vista 64bit and nothing on it but Vmware workstation 6.5 Vista Image, that ill be installed on a RAM Disk i will make on the main Vista.

now in this way the whole Vmware Image will be in RAM so i will install VS 2008 in it and put all my sites there as if it was a real disk, now i have made few tests on running Applications from RAM Disk and the performance was blazing, but i have some concerns.

• how i can make continuous backups, because as you know it is a RAM Disk and once the PC is restarted Everything is Gone and i will loose everything, VS, SQL DBs, and my sites.

-as long as my Main Host Vista will not have anything Installed is leaving 8 GB of Ram for it is enough ?

• as you know the VMware Image is one file, so should i Defrag the Host Drive or the Drive inside the VMware Image ?

thanks in Advanced.

Answer 1

To me this doesn't seem like a good idea, if the system goes down the ram disk is destroyed.

I would focus on simply allocating the ram in a helpful manner, and keeping the OS files on disk.

Answer 2

Have a look at Live Mesh. It will take care of synchronising all the data for you. When you reboot your RAM image it will pull the files back down. In general use the only difference you notice between a LiveMesh folder and a normal one is the folder icon.

Answer 3

Defragmentation: Here's what VMWare recommends: "first, run a defragmentation utility in the VM; second, use the WMware Workstation defragmentation tool; third, run a defragmentation utility on the host"

Backup: for my VMs, I use SynbackPro to run a timed backup of my project files to a SHARED folder on my host machine, then on the host I have SyncbackPro running a timed backup to an external drive. That way, no matter which VM I happen to be using, the external drive gets the backups.

Answer 4

RAM disk is a great idea in principle, but you might not gain as much as you think. First, its declared overhead is about 10%, but in our server it degraded the performance in about 30-40%. Second, when having a lot of memory at hand, the system cache can load most of your files into memory anyway, so effectively all your IO is done with the RAM.

This is based on our experience with our server, and it might to apply to your case. I would suggest you at least try to install everything directly on the OS, let it run for some time so all needed files are cached, and then check the performance. If it's similar to what you have with VMWare + RAM disk, it would be much easier for you to maintain.