Webserver Performance Issues - Analysis and Tuning

Web server:  -

It accepts the client requests and send to app server .But not all requests to go to app server.Only primary URL goes to app server.Images,gifs and jpegs all are stored in webserver. All secondary requests go to web server only.

For each user two connections established with web server. For example 100 users 200 connections for web server minimum , 30 to 40 for app server, 10 to 20 to DB server .

Web server Issues :

1) Connection pool management   -  No of connections increases CPU will be high,if number of connections low ,cpu usage also low but response time would be high,so we need effective way of connection management.
2) Caching  - load all images in memory of webserver .If we  retrieve every time from disk it would be ineffective caching management .

3) Images - Images should be less and file size should be less .So we need to compress files and reduce size. Do effective compress ratio to decrease high response time.

Zip and Rar compression formats.

Web server does compression and browser does un compression.Looking to header information we can say file is compressed or not.

4) Keep Alive Connection : Need to define suitable time for this.

5) Load Balancer : 

4) Threading issues

4) Memory leaks

5) High verbose


Counters:

Current Connections : The number of active connections 

cache hits % -  it should be 80 or 90% .Always try to keep max

cache misses - intially it should be high and gradullay it should come down

sizing - bytes sent/sec .bytes recieved/sec - it gives for specific web server and  we can determine using this load balancer effectively working or not.

requests/sec