Mailing-List: contact user-help@jmeter.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "JMeter Users List" <user@jmeter.apache.org>
Received-SPF: pass (athena.apache.org: domain of shettyd@gmail.com designates
 209.85.212.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAKF7fU-c9f+9LwCKQuAhFQ3AjMezdQ1ZP6Go=MdMupN7U4+EDQ@mail.gmail.com>
References: 
 <CAKF7fU-c9f+9LwCKQuAhFQ3AjMezdQ1ZP6Go=MdMupN7U4+EDQ@mail.gmail.com>
Date: Tue, 12 Aug 2014 08:24:55 -0700
Message-ID: 
 <CAKUYAYcSES03ri1R6T_Ldge9xqKU-0fZk4b=3Xs74+U=0xD7gQ@mail.gmail.com>
Subject: Re: jmeter - thread count limit
From: Deepak Shetty <shettyd@gmail.com>
To: JMeter Users List <user@jmeter.apache.org>
Content-Type: multipart/alternative; boundary=f46d041828160f426405007046d0

--f46d041828160f426405007046d0
Content-Type: text/plain; charset=UTF-8

Hi
>"docs mention there is no hard & fast rule, it depends on system
hardware/software config & how soon the server responds for APIs under
test."
This is the technically correct answer

>" lists a number between 200-300 for number of threads"
This is most likely a rule of thumb or a starting point (e.g. I will rarely
exceed 40 threads on my client PC)

>We now need to put more load on it
It depends on how you define "load" - *Usually* you mean the concurrent
usage that the server sees in which case option B is the correct one.(It's
possible you might be running a long running test , just to see whether
there are memory leaks or something like that and you are using "load" in
that context in which case you probably only need option A. - happens , but
rare)
However lets say you want to test out 10 users accessing your system at the
same time, for an hour , then you might want to use different users (rather
than using the same user or  10 users which means you might get better than
expected results due to server caching user details or something like that)
- in which case you do also need Option A to make Option B realistic.
However you cannot just increase the number of threads without limit ,
because at some point of time , either the JMeter machine or the network
might start slowing down your tests which would not happen in a real life
scenario - in which case you now need to add more JMeter machines (either
distributed or standalone) - What number of threads your system supports is
dependent on multiple factors and there is no way out of testing and
validating your results - This has probably been discussed numerous times
in the archives of these mailing lists.


regards
deepak


On Mon, Aug 11, 2014 at 6:06 PM, Shilpa Kulkarni <syk@payasonline.com>
wrote:

> Hi
>
> I have a question about thread count limit in jmeter. Some of the -
> slightly older documentation on the internet - lists a number between
> 200-300 for number of threads. Some docs mention there is no hard & fast
> rule, it depends on system hardware/software config & how soon the server
> responds for APIs under test.
>
> I have built a basic API test plan for a mobile/server type of application
> & tested for 2 users in csv file & thread count = 10. We now need to put
> more load on it & I was checking out for any guide lines here. What are my
> options? A + B or just one of them? Are there any other options?
> A. Increase number of users in csv file
> B. Increase thread count
>
> Thanks
> SK
>

--f46d041828160f426405007046d0--