Slow Compile speed

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Barry - 13 Aug 2007 14:53 GMT

Hi

I have the following hardware
1 Intel Processor 3.2G
2. 512mb RAM
3. Using Visual Studio 2005 / Visual Basic

I have a webproject with multiple project and it takes a lontime to build
solution, what must i do
1. Increase RAM to say 1.5 G
2. Get a new Processor

TIA
Barry

Reply to this Message

Jim Rand - 13 Aug 2007 15:16 GMT

I found VS 2005 to be really slow. Increasing the ram from 512mb to 1 gig
(max on my system) had a significant impact on performance - it brought it
from intolerable to tolerable.

> Hi
>
[quoted text clipped - 10 lines]
> TIA
> Barry

Reply to this Message

Jesse Houwing - 13 Aug 2007 16:22 GMT

Hello Jim,

> I found VS 2005 to be really slow. Increasing the ram from 512mb to 1
> gig (max on my system) had a significant impact on performance - it
[quoted text clipped - 13 lines]
>> TIA
>> Barry

Some tips to improve performance:
- Disabling the visrusscanner (or excluding the source directories) usually
helps a lot as well
- Invest in a real defragmentation tool (PerfectDisk, OO Defrag are good
ones)
- Put your Swap file on a different disk than your sources and visual studio

Apart from that my guess is that investing in memory and/or a faster harddrive
(say 10.000 rpm & 16MB cache) will give you much more performance gain than
a new processor. Newer processors usually aren't faster per-se, but have
multiple cores and/or hyperthreading. I'm not sure how much faster the compiler
gets when using either of those, my guess is that the overall performance
gain isn't that much over a single core environment.

--
Jesse Houwing
jesse.houwing at sogeti.n

Reply to this Message

UL-Tomten - 14 Aug 2007 10:58 GMT

On Aug 13, 5:22 pm, Jesse Houwing <jesse.houw...@newsgroup.nospam>
wrote:

> and/or a faster harddrive (say 10.000 rpm & 16MB cache)

Before investing in an expensive harddrive, use a RAM drive to emulate
a really fast harddrive (but get more RAM first, of course). For
example, I was mighty surprised when compilation of a WAP (VS2005 SP1)
sped up by exactly 0% when moving the project files and the ASP.NET
Temporary files to a RAM drive, but YMMV.

Reply to this Message

Frans Bouma [C# MVP] - 14 Aug 2007 09:05 GMT

> Hi
>
[quoted text clipped - 6 lines]
> build solution, what must i do 1. Increase RAM to say 1.5 G
> 2. Get a new Processor

    What others said: get at least 1GB ram, because then windows doesn't
have to swap that much, and also be sure your harddisks are fast (as
compiling means reading a lot of files). If you're working on a laptop:
forget it, it will never be fast.

    Web projects tend to be slow as well. I'm not sure if you're using a
web SITE project or a web project (i.e the project format they released
after vs.net 2005 was released).

    What also helps is to split up solutions as much as possible, thus:
keep all assemblies USED by your webapp in a separate solution and keep
your webapp in a different solution. This will make compiling less slow
as most of the work you'll do is in the webapp code so you just have to
compile that project every time :)

        FB

Signature

------------------------------------------------------------------------
Lead developer of LLBLGen Pro, the productive O/R mapper for .NET
LLBLGen Pro website: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------

Reply to this Message

Slow Compile speed

Free Magazines