Assemblies

#1

I have a few questions regarding assemblies.

1. What peformance overhead is involved in simply referencing an assembly?
2. Would it be better on performance to have re-usable code library in ONE
assembly or logically broken out into separate assemblies?
3. What performance overhead is involved when the application loads an
assembly that is referenced?

--
-Demetri

#2

You should also consider whether the referenced assemblies are registered in
the GAC or not. GAC assemblies only need to load once whereas private
assemblies load per application that uses it.

"Vadym Stetsyak" <vadym_s (AT) ukr (DOT) net> wrote

Quote:

Hello, Demetri!

D> 1. What peformance overhead is involved in simply referencing an
D> assembly?

Afaik a reference to assembly will look like additional record in some
meta data table, AFAIK assembly will not be loaded until code will
reference type contained in it.

D> 2. Would it be better on performance to have re-usable code library in
D> ONE assembly or logically broken out into separate assemblies?

It depends on quantity of assemblies. However, if there will be multiple
assemblies the overhead will be greater as they will comsume more memory
( there exists system info about every loaded assembly ). OTOH if use one
big assembly then time that takes this assembly to load may hurt
performance ( on application start ).

D> 3. What performance overhead is involved when the application loads an
assembly
D> that is referenced?

Talked about that earlier...

--
Regards, Vadym Stetsyak
www: http://vadmyst.blogspot.com

#3

"Scott M." <s-mar (AT) nospam (DOT) nospam> wrote

Quote:

You should also consider whether the referenced assemblies are registered
in
the GAC or not. GAC assemblies only need to load once whereas private
assemblies load per application that uses it.

This is not true, unless they are NGen'd assemblies.

Willy.

Quote:

"Vadym Stetsyak" <vadym_s (AT) ukr (DOT) net> wrote in message
news:eERKyofOGHA.344 (AT) TK2MSFTNGP11 (DOT) phx.gbl...
Hello, Demetri!

D> 1. What peformance overhead is involved in simply referencing an
D> assembly?

Afaik a reference to assembly will look like additional record in some
meta data table, AFAIK assembly will not be loaded until code will
reference type contained in it.

D> 2. Would it be better on performance to have re-usable code library
in
D> ONE assembly or logically broken out into separate assemblies?

It depends on quantity of assemblies. However, if there will be multiple
assemblies the overhead will be greater as they will comsume more memory
( there exists system info about every loaded assembly ). OTOH if use
one
big assembly then time that takes this assembly to load may hurt
performance ( on application start ).

D> 3. What performance overhead is involved when the application loads
an
assembly
D> that is referenced?

Talked about that earlier...

--
Regards, Vadym Stetsyak
www: http://vadmyst.blogspot.com

#4

Or... This is true, unless they're not NGEN'd.

"Willy Denoyette [MVP]" <willy.denoyette (AT) telenet (DOT) be> wrote

Quote:

"Scott M." <s-mar (AT) nospam (DOT) nospam> wrote in message
news:uZABvnuOGHA.344 (AT) TK2MSFTNGP11 (DOT) phx.gbl...
| You should also consider whether the referenced assemblies are
registered
in
| the GAC or not. GAC assemblies only need to load once whereas private
| assemblies load per application that uses it.
|
|

This is not true, unless they are NGen'd assemblies.

Willy.

| "Vadym Stetsyak" <vadym_s (AT) ukr (DOT) net> wrote in message
| news:eERKyofOGHA.344 (AT) TK2MSFTNGP11 (DOT) phx.gbl...
| > Hello, Demetri!
|
| > D> 1. What peformance overhead is involved in simply referencing an
| > D> assembly?
|
| > Afaik a reference to assembly will look like additional record in some
| > meta data table, AFAIK assembly will not be loaded until code will
| > reference type contained in it.
|
| > D> 2. Would it be better on performance to have re-usable code library
in
| > D> ONE assembly or logically broken out into separate assemblies?
|
| > It depends on quantity of assemblies. However, if there will be
multiple
| > assemblies the overhead will be greater as they will comsume more
memory
| > ( there exists system info about every loaded assembly ). OTOH if use
one
| > big assembly then time that takes this assembly to load may hurt
| > performance ( on application start ).
|
| > D> 3. What performance overhead is involved when the application loads
an
| > assembly
| > D> that is referenced?
|
| > Talked about that earlier...
|
| > --
| > Regards, Vadym Stetsyak
| > www: http://vadmyst.blogspot.com
|
|

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Assemblies

Dotnet Framework (Performance) microsoft.public.dotnet.framework.performance

Assemblies - 02-24-2006 , 09:58 AM

Re: Assemblies - 02-26-2006 , 10:33 AM

Re: Assemblies - 02-28-2006 , 05:37 PM

Re: Assemblies - 02-28-2006 , 10:20 PM