I am writing this blog after long time, this time I have decided to write something on IIS 6.0.
Most of us are having very little knowledge on IIS 6.0 configuration and we know very little about the capabilities of IIS 6.0. Being a technical guy, the person who is involved in application development should know in and out of all the configuations which will help us to develope scalable application. I mean to say that, whether person is a Sr Manager or a trainee developer he should know all these tricks.
Following are some of the tricks which we can use to scale up IIS 6.0
1. Recycle
Recycle IIS processes on certain interval , though IIS does it on every 29 hours. Right click on 'Application Pool' , click on 'Properties' . Follwing window will get displayed.
Even you can specify timing when IIS should recycle worker process or on number of requests.
2. Grow Web Garden
This is one of the way to increase application pool performance. Web garder helps in a scenariao when worker processes gets hanged and nother worker process can take care of incoming requests.
3. Enable HTTP Compression
Its better to compress pages which IIS is serving, but its not good to compress all the files.
Not all the requested pages are generated dynamically, for example static HTML files are not generated dynamically , so its better to compress these files using HTTP compression , so next time when IIS receives request for these static files, it will get it from the cache. IIS does not need to compress it again.
Right click on 'Web Sites' -> 'Properties' and click on 'Service' tab to enable HTTP compression.
4. Connection Timeouts
HTTP connections may keep open while user downloading files from the server, IIS terminates these connections after 120 seconds by default.But you can adjust these connection timeout accordingly.
5. HTTP Keep Alive.
IIS enables Keep-Alive by default. The main advantage behind HTTP Keep Alive is , it does not allow server to close and open server connection again and again. This helps to optimize server performance
Please note, only some part of scalability is achieved through IIS configuration, if your code is not well written, database design is not proper and has number of open connections etc ect, then above mentioned tricks are of no use.
Most of us are having very little knowledge on IIS 6.0 configuration and we know very little about the capabilities of IIS 6.0. Being a technical guy, the person who is involved in application development should know in and out of all the configuations which will help us to develope scalable application. I mean to say that, whether person is a Sr Manager or a trainee developer he should know all these tricks.
Following are some of the tricks which we can use to scale up IIS 6.0
1. Recycle
Recycle IIS processes on certain interval , though IIS does it on every 29 hours. Right click on 'Application Pool' , click on 'Properties' . Follwing window will get displayed.
Even you can specify timing when IIS should recycle worker process or on number of requests.
2. Grow Web Garden
This is one of the way to increase application pool performance. Web garder helps in a scenariao when worker processes gets hanged and nother worker process can take care of incoming requests.
3. Enable HTTP Compression
Its better to compress pages which IIS is serving, but its not good to compress all the files.
Not all the requested pages are generated dynamically, for example static HTML files are not generated dynamically , so its better to compress these files using HTTP compression , so next time when IIS receives request for these static files, it will get it from the cache. IIS does not need to compress it again.
Right click on 'Web Sites' -> 'Properties' and click on 'Service' tab to enable HTTP compression.
4. Connection Timeouts
HTTP connections may keep open while user downloading files from the server, IIS terminates these connections after 120 seconds by default.But you can adjust these connection timeout accordingly.
5. HTTP Keep Alive.
IIS enables Keep-Alive by default. The main advantage behind HTTP Keep Alive is , it does not allow server to close and open server connection again and again. This helps to optimize server performance
Please note, only some part of scalability is achieved through IIS configuration, if your code is not well written, database design is not proper and has number of open connections etc ect, then above mentioned tricks are of no use.
Comments