Click here to Skip to main content
Click here to Skip to main content

Best Strategy for deploying ASP.NET application and application Pool

, 23 Aug 2010
Rate this:
Please Sign up or sign in to vote.
Best Strategy for deploying ASP.NET application and application Pool
Hi,
 
I was exploring some aspect of deployment with respect to the asp.net application and application pool.
 
So the conclusion is :
 
If you want to share the security context, deploy them under the same application pool.With this setup, Keep in mind that by default you will get only 25 threads/cpu. If one collapses, all in that pool will get collapses.
 
Hence If your priority is for availability ,reliability and cpu bound then the best practice could be to Segregate the application( one application/pool).
 
I hope this helps!.
 
Regards,
-Vinayak

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

About the Author

Vinayaka Krishna Shenoy
Architect MindTree Ltd
India India
Motivated achiever who guides organizations in applying technology to business settings, provides added value, and creates project deliverables in a timely manner. An experienced Technical Consultant, have successfully led large project teams of more than 20 people from requirements gathering to implementation and support using C#, .NET ,ADO.NET, ADO.NET Entity Framework,ASP.NET,ASP.NET MVC, WCF and SQL Server.

Comments and Discussions

 
Questionwow what an explanation for app pooling!! PinmemberCallOfduty5-Aug-12 21:03 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

| Advertise | Privacy | Mobile
Web03 | 2.8.140721.1 | Last Updated 23 Aug 2010
Article Copyright 2010 by Vinayaka Krishna Shenoy
Everything else Copyright © CodeProject, 1999-2014
Terms of Service
Layout: fixed | fluid