Highlighted
Contributor.. Contributor..
Contributor..
654 views

Async Callbacks - Memory LEak for push conversation

Folks , 

 

Looks like we are dealing with a memory leak for Async Callbacks , a very bad one at that. 

 

Start a test with LR 11.52 on Windows 2003 with a push conversation. Running as threads seems to kill mmdrv as we see memory profile growing and then once it reaches ~ 1.3 GB it fails. We have done every thing possible in terms of cutting down operations in the ResponsebodyBuffer method and params- no luck so far. 

 

The App sends around 300-1000 bytes 3-4 times in a second. 

 

Running as a process gives us a bit longer test ,but nowhere near as needed. We need to also run 5k-8k , I dont believe with all the hardware we got we can do as a process( a mix of 4 chasis/Blades and 8 VMS )  as we are limited with around 400-500 users per physical hostwhen u run as a process on the chasis servers. 

 

12 seems to be a bit better but we cant move to 2008 on the physical servers yet 😞 

 

Raising a ticket with Support , in the meanwhile is there any tips or tricks to adjust this behaviour ? under the hood options ? Any ideas ? 

 

Thanks

Prabhu 

 

 

0 Likes
4 Replies
Highlighted
Absent Member.
Absent Member.

Hi prabhushankar,

 

Hope you are fine!

 

What is the protocol(s) you are using for that test?

How many Load generators are you using to test the script(s)?

 

Please provide us the above information.

 

Thanks and Regards,

 

 

AlexisB

0 Likes
Highlighted
Contributor.. Contributor..
Contributor..

Hi Alex ,
Regular HTTP protocol with Async callbacks implemented. Load generators as i mentioned earlier - a mix of 4 chasis/Blades and 8 VMS . But we were playing around in a couple of physical machines as they have more horse power.
We distinctly saw the mmdrv process memory used grow and once they reached beyond 1.2 GB all users will error out with Exception access memory violation erros.

thanks
Prabhu
0 Likes
Highlighted
Contributor.. Contributor..
Contributor..

So I assume no hacks available currently then..  😞 

0 Likes
Highlighted
Absent Member.
Absent Member.

Hi Prabhu

 I see that you are currently using two physical Server with more horsepower than  the mix of 4 Blad Server Chassis, it is an example of a Cisco Blade Server Chassis component and display architecturesand how it looks like I believe : http://www.cisco.com/c/dam/en/us/products/collateral/servers-unified-computing/ucs-b-series-blade-servers/spec_sheet_c17-644224.pdf.


I believe you need to remember that all the resources are imporntant you we are planning a heavy Performance Test. It is also depends on what type of Peformance Test you are trying to execute. There are some types such as:

    Load Testing.
    Stress Testing
    Soak Testing.
    Spike Testing
    Configuration Testing
    Isolation Testing

Also we need to know how complex are the JavaScript Asyncronous callbacks and how they play its roles during the execution. We need to reduce number of Vusers per Host, it means you may need to do a ramp up of vusers on Controller Scenario. We need to check if the server have
another processes being used, we need to discard or end the process that we do not need during the Load Test( for the 2 Host machines).

May you please let us know how many procotols are you using? Also What are the protocols being involved during the test, you can create a list of them?

Knowing the protocol we can find the possible causes that are producing this. Another recomendation is to redesign the script or scripts to ensure that it is run as separate iterations rather than repeatedly looping in a single iteration. This will ensure that memory allocated during the script iteration is released and thus prevent a memory leak occuring.

 

Kind Regards,

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.