papayamilkshake

 Profile Answers by papayamilkshake 

• May 15th, 2007

 

Setup the scenario with Available Bytes and Committed Bytes as one of the counters to monitor. Run the load test as per norm. Observe the pattern of memory usage on the designated server with the ramp up of Vusers and see if they correlate.

When the memory usage peaks at a ceiling, exit the Vusers gradually. If there wasn?t any leakage, the Available Bytes should increase and Committed Bytes decreased in correlation with the Vusers exiting. If it doesn?t, that is, the memory usage is persisted to be high, and the Vusers have successfully exited. It may indicate the memory leak existed in the application and will needed to be resolved (usually at the code-level). Code profiling tools such as Parasoft Jtest (etc.) will be useful in detecting potential poor coding standards.


More information provided in loadrunnertnt blogspot

gampatriveni

 Profile Answers by gampatriveni 

• Mar 17th, 2008

 

Hi,
According to my knowledge best way to detect memory leak is by conducting soak testing.

Let me know how many people agree with this answer nd let me know the correct answer if my answer is wrong.
Thanks

reachsanthan

 Profile Answers by reachsanthan 

• Apr 2nd, 2008

 

correlate Hits/sec graph with running Vuser graph, if you have any memory leak then hits/sec graph will be saturated it won't get spiked according to more number of vusers  gets in.