Is VS2005 optimized for ... ?

[Jarod]

Hey
Is VS2005 optimized for Intel or AMD processor ? What gives best speed when
I develop webprojects ? What really means in the term of speed 2 cores or
frequency I assume 64bits.
Jarod

[Nicholas Paldino [.NET/C# MVP]]

Jarod,

VS.NET 2005 isn't what you will want to be worried about. Rather, the
CLR is what you want to be concerned with, since it is what is doing the
compiling of IL into machine code.

As far as I know, the CLR doesn't have any processor-specific
optimizations. However, it is not outside of the realm of possibility that
support for processor-specific optimizations will come down the line in the
future (perhaps with the Phoenix project).

If you are asking if the actual IDE is optimized for your processor, I
would say no, it is not. Nor do I think that it would make that much of a
difference if it did.

A dual core machine is typically going to make a difference when a
program uses multiple threads of execution, but it's hard to make a general
statement like that. It has to be taken on a case-by-case basis.

The same can be said for 64-bit processors. It generally helps if the
program was compiled for 64 bits, which, as far as I know, VS.NET 2005 was
not.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com
"Jarod" <bl*****@NOSPAM.gazeta.pl> wrote in message
news:%2****************@TK2MSFTNGP15.phx.gbl...

Hey
Is VS2005 optimized for Intel or AMD processor ? What gives best speed
when I develop webprojects ? What really means in the term of speed 2
cores or frequency I assume 64bits.
Jarod

[Hans Kesting]

Isn't Visual Studio itself a .Net program? Then all your comments about
CLR Jitting apply equally to Visual Studio.

IIRC one of the puls-points for JITting *is* processor specific
optimizations. Now I don't know if that is actually used or a "possible
future enhancement".

Hans Kesting

Jarod,

VS.NET 2005 isn't what you will want to be worried about. Rather, the
CLR is what you want to be concerned with, since it is what is doing the
compiling of IL into machine code.

As far as I know, the CLR doesn't have any processor-specific
optimizations. However, it is not outside of the realm of possibility that
support for processor-specific optimizations will come down the line in the
future (perhaps with the Phoenix project).

If you are asking if the actual IDE is optimized for your processor, I
would say no, it is not. Nor do I think that it would make that much of a
difference if it did.

A dual core machine is typically going to make a difference when a
program uses multiple threads of execution, but it's hard to make a general
statement like that. It has to be taken on a case-by-case basis.

The same can be said for 64-bit processors. It generally helps if the
program was compiled for 64 bits, which, as far as I know, VS.NET 2005 was
not.

[Richard Blewett [DevelopMentor]]

"Hans Kesting" <ne***********@spamgourmet.com> wrote in message
news:mn***********************@spamgourmet.com...

Isn't Visual Studio itself a .Net program? Then all your comments about
CLR Jitting apply equally to Visual Studio.

IIRC one of the puls-points for JITting *is* processor specific
optimizations. Now I don't know if that is actually used or a "possible
future enhancement".

Hans Kesting

Visual Studio is mostly unmanaged code although significant pieces are
written in managed code

Regards

Richard Blewett - DevelopMentor
http://www.dotnetconsult.co.uk/weblog
http://www.dotnetconsult.co.uk

[Jarod]

> A dual core machine is typically going to make a difference when a

program uses multiple threads of execution, but it's hard to make a
general statement like that. It has to be taken on a case-by-case basis.

The same can be said for 64-bit processors. It generally helps if the
program was compiled for 64 bits, which, as far as I know, VS.NET 2005 was
not.

So more gigs will make the best diffrence ?
Jarod

[Nicholas Paldino [.NET/C# MVP]]

More gigs of what? Hard drive space? Memory? More memory is always
going to help, but more gigs on the hard drive isn't going to do much of
anything unless you are desperately low on space.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"Jarod" <bl*****@NOSPAM.gazeta.pl> wrote in message
news:O1**************@tk2msftngp13.phx.gbl...

A dual core machine is typically going to make a difference when a
program uses multiple threads of execution, but it's hard to make a
general statement like that. It has to be taken on a case-by-case basis.

The same can be said for 64-bit processors. It generally helps if the
program was compiled for 64 bits, which, as far as I know, VS.NET 2005
was not.

So more gigs will make the best diffrence ?
Jarod

[Jarod]

> More gigs of what? Hard drive space? Memory? More memory is always

going to help, but more gigs on the hard drive isn't going to do much of
anything unless you are desperately low on space.

I meant GHz ( this gigs ;) Memory above 1 GB I don't think it's going to be
helpful because even if you start a lof of apps you still have some free
place. HDD ... maybe SATA , but I don't think it will make me a diffrence.
Jarod

[Joe [MCAD]]

Jarod, the .net 2.0 framework/clr is supported on two kinds of processors
x86 and x64. VS2005 is the IDE for developing .net applications, i doubt
there is specific processor code in the IDE because its generally not
processing intensive; most of the time the application is waiting for your
input. If it seems sluggish on your machine see if windows is paging a lot,
you might not have enough memory. I had to do a memory upgrade when VS2003.

Joe

BTW... .net for 64bit machines, i believe you also need the 64bit version of
windows.
http://www.microsoft.com/downloads/d...displaylang=en
"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard.caspershouse.com> wrote in
message news:eG**************@TK2MSFTNGP12.phx.gbl...

Jarod,

VS.NET 2005 isn't what you will want to be worried about. Rather, the
CLR is what you want to be concerned with, since it is what is doing the
compiling of IL into machine code.

As far as I know, the CLR doesn't have any processor-specific
optimizations. However, it is not outside of the realm of possibility
that support for processor-specific optimizations will come down the line
in the future (perhaps with the Phoenix project).

If you are asking if the actual IDE is optimized for your processor, I
would say no, it is not. Nor do I think that it would make that much of a
difference if it did.

A dual core machine is typically going to make a difference when a
program uses multiple threads of execution, but it's hard to make a
general statement like that. It has to be taken on a case-by-case basis.

The same can be said for 64-bit processors. It generally helps if the
program was compiled for 64 bits, which, as far as I know, VS.NET 2005 was
not.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com
"Jarod" <bl*****@NOSPAM.gazeta.pl> wrote in message
news:%2****************@TK2MSFTNGP15.phx.gbl...

Hey
Is VS2005 optimized for Intel or AMD processor ? What gives best speed
when I develop webprojects ? What really means in the term of speed 2
cores or frequency I assume 64bits.
Jarod

[Jon Skeet [C# MVP]]

Jarod <bl*****@NOSPAM.gazeta.pl> wrote:

More gigs of what? Hard drive space? Memory? More memory is always
going to help, but more gigs on the hard drive isn't going to do much of
anything unless you are desperately low on space.

I meant GHz ( this gigs ;) Memory above 1 GB I don't think it's going to be
helpful because even if you start a lof of apps you still have some free
place. HDD ... maybe SATA , but I don't think it will make me a diffrence.

Memory over 1GB definitely *does* make a difference - because it means
Windows is able to cache a lot more files. Caching more => less disk
access => speed. This is particularly true for laptops, where the disk
is often the performance bottleneck.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too