The following is for archival purposes only. The latest builds of Dolphin now have this by default.
---
Note: This is for people seeking to compile dolphin builds from the repository. There is a site which compiles builds (although each takes an indefinite amount of time to start, and approx. 15 minutes to compile + upload).
My experience: My compile time has been reduced from 5 minutes to about a minute. I'm sure the only limiting factor now is my hard drive speed (don't have a solid state).
Tutorial (vs2008): (Note that this can be applied to any C++ project, not just dolphin):
1) Open the solution for Dolphin.
2) Right click on "Core".
3) Choose "Properties".
4) Go to Configuration Properties > C/C++ > Command Line.
5) In "Additional options", type "/MP" without quotes.
6) Compile, and note a significantly faster compile time. So far, I've discovered no pitfalls in using the MP (multiple processor) command option.
Assuming you have a relatively new processor, the limiting factor now should be your hard drive speed, unless you have a solid-state drive, in which case the limiting factor is probably still your processor.
You can read more about the MP option @ MSDN.
Note that if you want, you can specify the number yourself, or let Visual Studio determine the number of effective cores, which is in my case, 8.
---
Note: This is for people seeking to compile dolphin builds from the repository. There is a site which compiles builds (although each takes an indefinite amount of time to start, and approx. 15 minutes to compile + upload).
My experience: My compile time has been reduced from 5 minutes to about a minute. I'm sure the only limiting factor now is my hard drive speed (don't have a solid state).
Tutorial (vs2008): (Note that this can be applied to any C++ project, not just dolphin):
1) Open the solution for Dolphin.
2) Right click on "Core".
3) Choose "Properties".
4) Go to Configuration Properties > C/C++ > Command Line.
5) In "Additional options", type "/MP" without quotes.
6) Compile, and note a significantly faster compile time. So far, I've discovered no pitfalls in using the MP (multiple processor) command option.
Assuming you have a relatively new processor, the limiting factor now should be your hard drive speed, unless you have a solid-state drive, in which case the limiting factor is probably still your processor.
You can read more about the MP option @ MSDN.
Note that if you want, you can specify the number yourself, or let Visual Studio determine the number of effective cores, which is in my case, 8.
![[Image: stats.png]](http://dl.dropbox.com/u/6039796/stats.png)