Performance Issue : Large number of queued requests on the application server, but the application server usage is low...

Large number of queued requests on the application server, but the application server usage is low.

What could be the issue?

How to find out performance issues from resource level

1) Memory based

a. Pages/sec > 10

b. Page Faults/sec > Cache Faults/sec AND Committed Bytes is more than Physical Memory

2) Processor based

a. If system: % Total Processor Time averages near 100% & system:

Processor Queue Length averages more than 2. (Run for at least 2 hours)

Performance Counters

Client Side Statistics

•Running Vusers

•Hits per Second

•Throughput

•HTTP Status Code

•HTTP responses per Second

•Pages downloaded per Second

•Transaction response time

•Page Component breakdown time

•Page Download time

•Component size Analysis

•Error Statistics

•Errors per Second

•Total Successful/Failed Transactions

Server Side Statistics

•System Resources

–CPU, Memory, Disk I/O

•Web Server Resources

–Threads, Cache Hit Ratio

•Application Server Resources

–Heap size, JDBC Connection Pool

•Database Server Resources

–Wait Events, SQL Queries

•Transaction Profiling

- Code Block Analysis

Network Monitoring

•Bandwidth Utilization

•Network delay time

•Network Segment delay time

Do's and Don'ts in Load Testing

Do’s :

Ø Providing admin rights and start up health check on the servers for monitoring before ten minutes.

Ø Schedule a dedicated time frame and environment for the load test.

Ø Clearing all the logs and stopping unnecessary Processes.

Ø Creating a checklist on environment and application changes.

Ø Creating folders for results, test scripts and test runs on the test runs executed.

Ø Conducting Baseline tests before and after tuning.

Ø Restarting the application after each successful run.

DON’Ts:

Ø Browsing through the application during load testing.

Ø Start of any activity (Virus Scan)

Ø Opening the monitoring tools during load testing.

Ø Changing configuration settings of application server or database server during load testing.

Ø Connecting to remote machine from either the load machine or the controller machine.

Ø Execute batch processes during the test

Ø Usage of network during the test.