In this series, I’ll discuss how to the steps that I did to improve VS 2008/2012/2012 performance. Following these guidelines, I managed to reduce build time from +10sec to 3-5sec , and solution opening time from 20+ sec to just mere 5sec.
For some may think “a few sec ain’t a big deal”, I would like to stress: it’s really make a different when you test & debug. Anyway, what else will you do when VS is compiling ? Thinking of what to do with your life ? 
. Life’s better when you can cut down build time and spent that on other hobby (for me it’s building performance workstation- I just upgrade mine to 16GB DDR3-2000Mhz with RAID10 SSD ^^ )
OK enough chit chat, now back to the main point.
1.Requirements:
Before proceed with the guide, ensure that your machine meet these minimum requirements:
- At least 2Gb free memory.
- Core2Duo 1.8Ghz (dual-core) or equivalent AMD multicore.
- At least 5Gb free HDD space.
2.Steps:
a. First, if you have lots of RAM (4GB+ ), you can use Ramdisk to create a separate partition, then map your output folder to it.
I downloaded Ramdisk , then install it. Using the tool, I created the symbolic link from the VS output folder via mklink :
C:\mklink /D "F:/RamdiskTemp/Src/bin" "C:/Work/Web/Src/bin"
symbolic link created for "F:/RamdiskTemp/Src/bin" <<===>> "C:/Work/Web/Src/bin"
b. Use the same mklink tool, create symbolic link for your ASP.NET temp folder, point tothe newly created Ramdisk.
The ASP.NET temp folder (for .NET 4.0) is at :
C:\windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files (64bit)
C:\windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files(32bit)
c. Use eBoostr to implement cache at OS-level for your VS. I used 512MB of memory to cache.
Detail of how to use eBoostr, please refer to their website.
<<to be continue>>
No comments:
Post a Comment