|
|
|
start date: Mon, 13 Aug 2007 19:23:53 +0530,
posted on: microsoft.public.dotnet.framework
back
| Thread Index |
|
1
Barry
|
|
2
Jim Rand
|
|
3
Jesse Houwing am
|
|
4
UL-Tomten
|
|
5
Frans Bouma [C# MVP]
|
Slow Compile speed
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
Date:Mon, 13 Aug 2007 19:23:53 +0530
Author:
|
Re: Slow Compile speed
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.
"Barry" wrote in message
news:%23%23NkjFb3HHA.4400@TK2MSFTNGP06.phx.gbl...
> 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
>
Date:Mon, 13 Aug 2007 10:16:13 -0400
Author:
|
Re: Slow Compile speed
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
> brought it from intolerable to tolerable.
>
> "Barry" wrote in message
> news:%23%23NkjFb3HHA.4400@TK2MSFTNGP06.phx.gbl...
>
>> 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
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.nl
Date:Mon, 13 Aug 2007 15:22:01 +0000 (UTC)
Author:
|
Re: Slow Compile speed
Barry wrote:
> 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
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
--
------------------------------------------------------------------------
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#)
------------------------------------------------------------------------
Date:Tue, 14 Aug 2007 01:05:13 -0700
Author:
|
Re: Slow Compile speed
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.
Date:Tue, 14 Aug 2007 02:58:49 -0700
Author:
|
|
|