Forums Register Login

Mercury Load Runner - Stress Test Performance Issue

+Pie Number of slices to send: Send
Hi,

Currently, my web application is deployed two different environment.

First environment server 1, this one not secured site(http), and also this is intranet, to test locally.
Second environment server 2, this one is secured site(https), and also this is internet, this environemt for users to test the application.

When i am running Mercury load runner stress test, in server 1, http, it finish very fast, the average transaction time is 1 second. The same application, when i am running server 2, secured site and also using proxy to connect internet, it takes 12 seconds to finish the transaction.

My question,

Both server having same code, it takes different time why?
Server2 is secured site and also using proxy that is the reason the application is slow or is there any other reason?

Is there any way to increase the spead, and reduce the transaction time in server2?

Any one having the experience in Mercury loadrunner using proxy, need your advice

thanks
chidam
+Pie Number of slices to send: Send
A lot of things can cause the difference in performance including:

Firewalls
Hardware capacity differences
Load on the hardware (i.e., other applications consuming resources)
Network congestion
Configuration differences (i.e., log level, thread pool exhaustion, db connection pool exhaustion)
Database performance (i.e., poor query performance due to invalid statistics, number of rows being queried.)

The only way to determine what the problem is will be to enable an application monitor (like WebSphere's WSAM) and drill down to see which method calls are taking the longest.

If you can't get access to an application monitor, add a small amount of logging to your methods to determine which are running the longest.

Once you know where the time is being spent you can dig in and find the root cause.

It's likely you have more than one issue so after you fix one problem keep digging.
[ October 11, 2006: Message edited by: Scott Johnson ]
+Pie Number of slices to send: Send
What is your stress load(number of concurrent requests) in server 1 & server 2 ?
+Pie Number of slices to send: Send
it takes different time duration to complete single transaction.
+Pie Number of slices to send: Send
 

it takes different time duration to complete single transaction.



Yes, I'm sure it does.

As I mentioned before, you need to determine which methods are slow and then determine why.

Which method(s) in your code are running longer than 1 second? (Not high level methods -- drill as far down the call stack as you can go.)

If you don't already have an app monitor, take a look at JAMon.
The moth suit and wings road is much more exciting than taxes. Or this tiny ad:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com


reply
reply
This thread has been viewed 3997 times.
Similar Threads
Starting an application on server2 using wsadmin/jacl
Advantages And Disavantages Of Tomcat
Mercury Load runner: where to take HTTP header?
Stress Vs Load Testing
planning to desing a stress test tool
More...

All times above are in ranch (not your local) time.
The current ranch time is
Mar 29, 2024 02:08:43.