jmeter-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jomebrew <>
Subject Re: Unable to run for 500 threads
Date Thu, 13 Jun 2013 14:48:29 GMT
I run exclusively in GUI mode and run two thread groups with 250 threads
each.  They share data and thread groups and run perpetually.  I am running
on an older 2ghz dual quad core server.  I can run four instances of this
scenario with a total of 2000 threads.   One thread group is in a tight
loop waiting for events and one thread group is sending different requests
based on a random chance.   Each instance of the four instances handles a
couple hundred thousand transactions to a million a day.  I run instances
for a few days to a week.

I use the Simple Data Writer, View Results Tree (for errors only), Results
Summary and Aggregate report in GUI mode.  I should try non-gui mode one
day but I like looking at aggregate report data.

This will use about 90% of CPU and about 4GB memory.  JMeter 2.9 uses a lot
more CPU but less memory than 2.6.

On Thu, Jun 13, 2013 at 5:12 AM, Saranya C <>wrote:

> Hi,
> I am trying to run a test with 500 threads, with 100 threads each
> distributed across 5 thread groups. But when i start the test, it hangs
> immediately after around a minute or two.
> It shows the count of threads somewhere near 20 and entire jmeter gets
> stuck. Nothing could be done after that.
> Is this because of the system specifications (2GB RAM; 40 GB HDD) or ????
> Thanks in Advance,
> Saranya C
> ==============================================================================================================================================================
> Disclaimer: This message is intended only for the individual or entity to
> which it is addressed. It may contain privileged, confidential information
> which is exempt from disclosure under applicable laws. If you are not the
> intended recipient, please note that you are strictly prohibited from
> disseminating or distributing this information (other than to the intended
> recipient) or copying this information. If you have received this
> communication in error, please notify us immediately by return email.
> ==============================================================================================================================================================

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message