Four ASP.NET performance & scalability secrets

ASP.NET is a powerful web application development framework. Developer across the globe love to work on this tech because it will allow them to tweak anything they want. Day by day this platform is becoming more mature and Microsoft regularly updates it and add fresh features in its code. All these innovative features of ASP.NET allow web developers to build and manage a variety of high-performance and highly scalable web application at a rapid pace.

However, each developer also needs to learn few tips and tricks that come in handy while carrying out the .NET Application Development process. The combination of advanced features and simple changes would surely make it easier for the programmers to create web apps that offer amazing user experience. Here are four tricks that will boost the performance and scalability of ASP.NET apps:

1. Configuration: The System.NET comes pre-configured and allows two concurrent connections for each IP. So the web server can make only two concurrent calls, and the outbound call to the specific server or calling WCF service on another server. A similar thing happens to the web application, the number of connection will also put an adverse effect while using different web services. So you should change the System.NET config to machine.config or web.config to pump up the performance.

2. WCF Default Configuration: By default, the WCF configuration allows to make only 16 concurrent calls per each service. Also, the default number of concurrent calls is now reduced to 10, so in case you are using sessions and wsHttpBinding then the default number will not be adequate to meet the needs of sites which fetch high web traffic. To overcome this issue during the .NET Web Development you should use InstancePerContext.PerCall set which will ensure that each request is handled by building a new instance of the service.

3. Process Model Configuration: The process level properties of an ASP.NET application which are defined in Process Model Configuration. Well, this configuration defines the number of threads used by an app, the number of requests which are kept in waiting and the whole duration of blocking the thread before the timeout. As the default value of each process level of property, it can affect the scalability & performance of your web app. To eliminate this issue, you must reset the default values for maxWorkerThreads, maxIOThreads and minWorkerThreads.

4. Enable Caching and Dynamic Compression on IIS: Apart from making changes in the ASP.NET config you also need to modify the IIS configuration so that you can easily make your dynamic web applications more scalable and stable. For instance, if the dynamic content compression option is disabled then it will definitely go to put a negative impact on the output from the WCF (Windows Communication Framework) and ASP.NET pages. It will be good that you must turn on the IIS compression for both static and dynamic content. Sometimes Enable Dynamic Content Compression feature remains disabled by default make sure you change it before moving further.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

Create a free website or blog at

Up ↑

%d bloggers like this: