How do I speed up sharepoint development in Virtual PC?
Things we did before we switched to Hyper-V ...
Don't allocate too much RAM to the VPC, it will start using the paging file too much.
Make sure virtual hard disks and virtual memory files for VPC are excluded from your antivirus software.
Defrag the VPC, then defrag the host.
You do not have a paging file on the same disk as your VPC.
Eliminate the size of the paging file so it does not become fragmented.
Kill any background processes on your main host that you don't need to start to do your job ... and for that matter, tune Windows for better performance, not better looks.
Start a virtual server, not a virtual PC, and use remote desktop to access the VPC (I found VS to be a little better at managing machines, and remote desktop seems to be faster and provides a nice full screen to the second monitor).
I am running sharepoint on an external harrdrive. The VPC has a dedicated memory of 2.5 GB. It works pretty fast (not very fast, but workable).
So my advice is to allocate as much VPC memory as you can afford and run on an external hard drive. Use Fire Wire to connect your hard drive if possible, it makes a huge difference over USB.
Apart from this defragmenting your host machine and virtual machine can help (but can take ages).
source to share
Start something else. A virtual PC is garbage. Much better alternatives are available between HyperV, VMWare, and Virtualbox.
I personally use VMWare server. I tried HyperV but the performance was not what Microsoft expected. The fact that VMWare is available on three platforms means that I can run my projects on a Macbook, transfer it to a Linux server, or open it in another window.
And I can choose 1,2 or 4 cores.
source to share
Check out Scott Hanselman's Virtual Machine Performance Test . This is a general article on how to improve the performance of your virtual machine.
source to share
Use an SSD hard drive instead of HDD. There is a significant improvement in performance, especially in overpressure situations when a disk change occurs.
Also check that the .NET Framework does not check the CRL . If there is a problem with the network connection, you will get timeouts.
source to share