BOTTLE NECKS In The Applications

BOTTLE NECK : 1

Hits/sec:- I  design the scenario for 2000users in 2hrs test execution.

Issue: In 2hr the test execution I observe hits/sec is completely getting down to zero after 19min of test execution. But still the users are running constantly.

Observation:  I observe during the load test execution the web server was completely down at 19 min of the test execution and the application is not accessible by manual.

Recommendation: Recommend to the development team to do the tuning exercise to resolve in the web servers to get continues response for 2hr load test.

Resolution: the development team did some type of tuning to maintain the concurrence load for 2hrs test execution. The development team shares the resolution as shown below.

  

1. Apply the tuning exercise on web server concurrent connection to reduce the queue.

2. Apply the tuning exercise at runtime memory allocated to release the memory throughout the test execution by GC (garbage collector).

BOTTLE NECK : 2

Throughput:

  

Scenario:

         I design the scenario for 1000 users with 2 hours test execution.

ISSUE:

I observe during load test execution throughput behavior is normal until 19 min test and after that I observe throughput is completely down to zero.

Observation:

I observe during the load test execution was completely down at 19min of the test execution and the application is not accessible by manual. I also observe hit/sec is also simulate through the throughput graph which is causing the web server down.

Recommendation:

Recommended to the development team to do the tuning exercise to resolve in the web server to get response for 2 hours load test.

Resolution: the development team did some type of tuning to maintain the concurrence load for 2hrs test execution. The development team shares the resolution as shown below.

 

1. Apply the tuning exercise on web server concurrent connection to reduce the queue.

2. Apply the tuning exercise at runtime memory allocated to release the memory throughout the test execution by GC (garbage collector).

BOTTLE NECK : 3

Scenario:

Design the scenario for 5000 users with 4 hrs test execution which includes 1 hr ramp up time duration 2 hours.

Issue:

I observe the throughput 5000 users is gradually increase till 3000 users load on server and after that it become constant even if the load is gradual into 5000 users.

Observation:

I observe the network band width is utilizing maximum of 10MB which is available. So band width utilization is reaching to maximum available limit. Where it cannot access for the data to be transfer.

Recommendation:

        Recommend to the network administrator to increase  the bandwidth.

Resolution:

For the next test execution they increase the band width size from 10mbps to 20mbps.I have not observe any throughput issue in any next test runs.

BOTTLE NECK : 4

Scenario: 

I design the scenario for 1000 users in 10 hrs Endurance testing.

Issue:

I started  running endurance test as for 10 hrs duration but, I observe after the  6^th hour all the transaction is failed and in the web logic server console I observe it keeps on throwing out of memory exception .

Observation:

I observe after 6 hour execution the jvm heap memory is getting down to zero and out of memory exception web logic server console. This is causing the memory leak.

Recommendation:

I recommended to the developer team to resolve the memory leaks in the application.

Resolution:

1.     The development team did some kind of tuning exercise and again I run the same test but I have not observe any memory leaks code tuning execution.

2.     After the code tuning still I observe the same issue. So we once again recommend to the development team to increase heap size 512MB to 1024MB and value is same time after increasing same. But I have not observed any memory leaks in the execution.  

BOTTLE NECK : 5

SCENARIO:

     I design the scenario with 2000 concurrent users for 2hrs test execution.

Issue:

 I observe after 1hr test execution all the database transactions are getting failed.

Observation:

  When ever I observe all the database transaction getting failed. I was looking in to JDBC connection to analyze is there any problem with connection establish from application server to database server.But I observe in the connection pool the maximum connection configuration 50.But during the load test execution all the connections are inactive and it is not establish the new connection to talk with database.

Recommendation:

     

 I recommend to the development team to increase the JDBC connection in connection pool.

Resolution:

  The development team to increase the JDBC connection from 50 to 200.And after that I run the same test, but I have not observe any JDBC connection issues.

BOTTLE NECK : 6

SCENARIO:

 I design the scenario for 1000 vusers with 2hrs test execution.

Issue:

 I observed in the test analysis one of the avg transaction response time is 28sec but the expected SLA is 6sec.I analyze the corressponding transaction is intracted with the database.

Observation:

 

 To drill down the above issue I took a help of DBA team and I run AWR reports to trace the top SQL statements. The DBA team identify there is a query which is causing high transactions response time which is belong to the current issue.

Recommendation:

     

I recommended to DBA team to apply a query tuning to reduce the response time to the quarry.

Resolution:

  After the quarry tuning I run the same test again now I observed the avg response time < 6.