Should I store my code/projects on my SSD or my secondary drive?

I just got a new box.

It has an SSD for the primary drive and a 1TB SATA hard disk for the secondary drive.

I'm going to run Windows OS and my binaries on the SSD
and keep all my downloads/documents/music/etc on the secondary drive.

My question is, should I also keep my Visual Studio Projects and code on the SSD, or keep them on the secondary drive?

The faster SSD would presumably be better for compiling and indexed searches, but would it be better to keep it on the 2nd drive for a more parallel disk IO situation?

Solution 1:

SSD have a much better IO and therefore it makes sense to have your code on the SSD disk.

Solution 2:

It depends on the drive you have. The read is will always lose to the SSD, but maybe not on the write performance. Write performance is going to be important during compilations for creating new executables, assemblies and other build artifacts.

Copy one of your larger solutions to the HD and the SSD and compile both. You'll notice the difference one way or the other and have your decision. My guess is the HD will be faster for compiles/builds but the ssd will win everythig else.

Solution 3:

I don't know if this is possible in Visual Studio, but the best may be a combination of the two. Put the source code on the SSD, but have the compiled objects written to the HD. This is how we have out make based projects layed out, but for other reasons.