Home
Articles
Interview Questions
Download
Contact Us
.Net
.Net Design Pattern
.Net Windows Service
ADO.NET
Android
Architecture
ASP.NET Ajax
ASP.NET Core
ASP.NET Gridview
ASP.NET MVC
ASP.NET Web API
Automation Anywhere
AWS
AWS SDK and C#
AWS SDK and Node.js
Azure DevOps
Blockchain
Bootstrap
C#
CSS
Django
Docker
Environment
Excel
Excel Formula
Firebase
Flutter and dart
Git
HTML
HTML 5
IIS
Java
JavaScript
JMeter
JQuery
JSON
Light Switch 2011
Linux
Matplotlib
Microsoft Bot Framework
Microsoft Azure
MongoDB
MSWord
Node.js
NumPy
Pandas
Photoshop
PHP
PHP Codeigniter
PostGreSQL
Powerpoint
PowerShell
Project Management
Python
React.js
Seaborn
Selenium
Silverlight
Software Testing
Sonarqube
Spacy
SQL Server
UiPath
VBA For Excel
VBA For Outlook
WCF
WPF
XML
XSD
Articles
→
IIS
→
Different IIS Isolation Levels
Different IIS Isolation Levels
Low (IIS Process) → ASP pages run in INetInfo.Exe, the main IIS process, therefore they are executed in-process. This is the fastest setting, and is the default under IIS4. The problem is that if ASP crashes, IIS crashes as well.
Medium (Pooled) → In this case ASP runs in a different process than IIS, which makes this setting more reliable: if ASP crashes IIS won't. All the ASP applications at the medium isolation level share the same process, so you can have a web site running with just two processes (IIS and ASP process)
High (Isolated) → Each ASP application runs out-process in its own process space, therefore if an ASP application crashes, neither IIS nor any other ASP application will be affected. The downside is that you consume more memory and resources
Posted By -
Karan Gupta
Posted On -
Wednesday, June 8, 2022
Query/Feedback
Your Email Id
*
*
Subject
*
Query/Feedback
Characters remaining 250
*
*