Mailing-List: contact jmeter-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "JMeter Users List" <jmeter-user@jakarta.apache.org>
Received-SPF: pass (nike.apache.org: domain of sebbaz@gmail.com designates
 209.85.220.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1317214139942-4849000.post@n5.nabble.com>
References: <1317214139942-4849000.post@n5.nabble.com>
Date: Wed, 28 Sep 2011 13:56:17 +0100
Message-ID: 
 <CAOGo0VaCjO0dVTWs8yTDk11jJav6cARBMqRj0n+dLur8bTeNTg@mail.gmail.com>
Subject: Re: Distributed testing - Memory usage
From: sebb <sebbaz@gmail.com>
To: JMeter Users List <jmeter-user@jakarta.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

On 28 September 2011 13:48, poox <rb@bancha.net> wrote:
> Hi, I'm trying to run a fairly simple test plan in distributed mode and
> experiencing some interesting memory consumption issues which I hope someone
> can shed some light on..
>
> The problem is regardless of how many threads I use, each of the slave
> servers sees growing memory usage until they eventually run out of memory
> and the jmeter-server process dies with this error:
> java.lang.OutOfMemoryError: Java heap space
>
> I am very confused by this behaviour as my understanding of the slave mode
> jmeter-server is that it should be passing all data back to the master and
> the JVM GCs should be taking care of the memory, sadly this is not the case.
>
> Regardless of how many threads I use, with or without a constant timer etc..
> the memory usage of the java process on each of the slaves ramps up...
>
> Config:
> 1 x Master Server - Linux, GUI mode (CentOS x64)
> 3 x Slave Server - Linux (CentOS x64)
>
> Test plan:
> - 10,000 loops @ 5 threads
> - One thread group
> - Constant Timer (500ms)
> - 15 HTTP Requests (using HTTP client, non ssl.)

Any functions or other test elements (post-processor etc)?

> - One listener (Aggregate report)

Aggregate Listener used to use a lot of memory; remove all Listeners
from the test plan, and use -l on the client.

> Any ideas?

JMeter Version?

> Things I've tried:
> - Simple test plans.
> - Upping heap size on master + slaves to 1024
> - Batch mode processing for results

What do you mean by that?
Have you tried running the script non-GUI on the server?

> - Removing all listeners
>
> Tearing my hair out!
>
> --
> View this message in context: http://jmeter.512774.n5.nabble.com/Distributed-testing-Memory-usage-tp4849000p4849000.html
> Sent from the JMeter - User mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org