Prev: How does the Application Domain affect the reliability for the Aspnet_wp.exe
Next: Inconsistent behaviour Powershell Get-Recipient (Exchange 2010)
From: Tony Johansson on 2 May 2010 10:52
Hi!

Here is the question: "Which of the follwing are valid reasons to create an
application domain ?"
(Choose all that apply)

A. It is the only way to launch a separe process.
B. You can remove the application domain to free up resources.
C. Application domain improve performance.
D. Application domain provide a layer of separate separation and sequrity.

According to the book is the correct answer B and D.
My comment I do aggre to these two answers but also want to add answer C.

I mean if you use processes instead of app domain and have 10 processes for
10 identical exe assembly compare to
have 10 app domain under a parent process. In this example the performance
will be better if you have 10 app domain instead of 10 processes. So as a
summary I mean that to use app domain will increase the performance.

Does anyone agree with me ?
//Tony



From: Family Tree Mike on 2 May 2010 11:34
On 5/2/2010 10:52 AM, Tony Johansson wrote:
> Hi!
>
> Here is the question: "Which of the follwing are valid reasons to create an
> application domain ?"
> (Choose all that apply)
>
> A. It is the only way to launch a separe process.
> B. You can remove the application domain to free up resources.
> C. Application domain improve performance.
> D. Application domain provide a layer of separate separation and sequrity.
>
> According to the book is the correct answer B and D.
> My comment I do aggre to these two answers but also want to add answer C.
>
> I mean if you use processes instead of app domain and have 10 processes for
> 10 identical exe assembly compare to
> have 10 app domain under a parent process. In this example the performance
> will be better if you have 10 app domain instead of 10 processes. So as a
> summary I mean that to use app domain will increase the performance.
>
> Does anyone agree with me ?
> //Tony
>
>
>

Your discussion of the 10 app domains under one process assumes a
singular use of app domains. I don't believe this would be the
strongest argument for answer C.

I believe a stronger argument would be that assemblies no longer needed
can be removed, thus potentially freeing some memory resources. I'm not
sure you could state any degree of improved performance from this argument.

--
Mike
From: Patrice on 2 May 2010 12:07
B & D are always true whatever you are doing (by design you can unload an
AppDomain and they are separated hence more secure, you have no way to setup
this another way).

With C and as you don't know what is the context this is not the case (and
because of the separation it could decrease performance, for example I
believe the System.Addins mechanism uses this for isolation but then you
likely slightly decrease the performance as you cross domain boundaries).
IMO avoid being too smart. Either it's true and then select this response,
if you need to do some additional hypothesis to select the C response don't
select the response.

--
Patrice



"Tony Johansson" <johansson.andersson(a)telia.com> a �crit dans le message de
news:e9keZcg6KHA.5476(a)TK2MSFTNGP06.phx.gbl...
> Hi!
>
> Here is the question: "Which of the follwing are valid reasons to create
> an application domain ?"
> (Choose all that apply)
>
> A. It is the only way to launch a separe process.
> B. You can remove the application domain to free up resources.
> C. Application domain improve performance.
> D. Application domain provide a layer of separate separation and sequrity.
>
> According to the book is the correct answer B and D.
> My comment I do aggre to these two answers but also want to add answer C.
>
> I mean if you use processes instead of app domain and have 10 processes
> for 10 identical exe assembly compare to
> have 10 app domain under a parent process. In this example the performance
> will be better if you have 10 app domain instead of 10 processes. So as a
> summary I mean that to use app domain will increase the performance.
>
> Does anyone agree with me ?
> //Tony
>
>
>

From: Arne Vajhøj on 2 May 2010 15:45
On 02-05-2010 10:52, Tony Johansson wrote:
> Here is the question: "Which of the follwing are valid reasons to create an
> application domain ?"
> (Choose all that apply)
>
> A. It is the only way to launch a separe process.
> B. You can remove the application domain to free up resources.
> C. Application domain improve performance.
> D. Application domain provide a layer of separate separation and sequrity.
>
> According to the book is the correct answer B and D.
> My comment I do aggre to these two answers but also want to add answer C.
>
> I mean if you use processes instead of app domain and have 10 processes for
> 10 identical exe assembly compare to
> have 10 app domain under a parent process. In this example the performance
> will be better if you have 10 app domain instead of 10 processes. So as a
> summary I mean that to use app domain will increase the performance.
>
> Does anyone agree with me ?

10 processes will likely use more resources than 1 process.

But you are assuming that the alternative to 1 process with
10 app domains is 10 processes with 1 app domain, but the
alternative could just as well be 1 process with 1 app domain.

The reasons to prefer the 1/10 over the 1/1 is B and D.

Arne
 | 
Pages: 1
Prev: How does the Application Domain affect the reliability for the Aspnet_wp.exe
Next: Inconsistent behaviour Powershell Get-Recipient (Exchange 2010)