You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by Rajiv Nanduani <ra...@gmail.com> on 2017/11/13 16:53:40 UTC
how many threads we can run with webdriver sampler
hi, i would like to know through jmeter using webdriver sampler how many
threads we can run as it says it depends on CPU core.
thanks
Re: how many threads we can run with webdriver sampler
Posted by Deepak Shetty <sh...@gmail.com>.
Hi
The short answer is you need to figure out the number that works for you on
your test infrastructure for your test application and that you need to
validate your observations.
The longer answer is - first you need to differentiate between How many
could I theoretically launch v/s How many could I launch and still generate
the load with high degree of fidelity. For e.g. if JMeter says it is
running 100 threads concurrently , are you really seeing ~100 requests at
the same time on your server ?. Assuming you mean the latter then many more
factors come into play . To use an analogy - the question you are asking is
akin to "how many browser tabs can you open on your laptop ? " - Does it
matter if you are browsing a site or whether you are streaming a movie or
god forbid accessing a site with flash ?
So you need to look at CPU , memory , network and your test and your
application (for e.g. if your test has largish think times and your
applications take a few seconds to respond , its quite possible to simulate
a higher number of users )
WebDriver does take up more resources than normal HTTP Samplers so the load
you can generate is lower. I havent used the later versions of Selenium but
the older ones did really drive a browser instance so the question did
genuinely become how many browsers could run with reasonable speed on the
test machine.
>C = B + 1 where C = Number of Cores of the host running the test and N =
Number of Browser (threads).
Assuming that you want 0 overhead and no switching etc. If your tests have
0 think times and your requests respond very quickly maybe you might start
with this formula- Usually you will use higher values than this.
On Mon, Nov 13, 2017 at 8:27 PM, Rajiv Nanduani <
rajivkumarnandvani@gmail.com> wrote:
> thanks bob for the reply but i am surprised with this number like 2000 or
> 10k while it says if your CPU core like 4 processor than you can use upto 3
> threads please see below references so i am confused now which is is
> correct?
>
> Meter allows the creation of multiple threads, and each thread is
> responsible for creating load on the server. However, for the Web Driver
> use case, the reader should be prudent in the number of threads they will
> create as each thread will have a single browser instance associated with
> it. Each browser consumes a significant amount of resources, and a limit
> should be placed on how many browsers the reader should create. However,
> the load testing cloud providers may help to scale WebDriver test up to
> thousands of real browsers, look at BlazeMeter
> <http://blazemeter.com/?utm_source=jmplinnerpages&utm_
> medium=cpc&utm_content=jmpininnerpgs&utm_campaign=WebDriverPlugin>
> for
> example.
>
> From experience, the number of browser (threads) that the reader creates
> should be limited by the following formula:
>
> C = B + 1
>
> where C = Number of Cores of the host running the test
> and N = Number of Browser (threads).
>
> eg, if the current reader's host has 4 cores, the formula would yield:
>
> 4 = 3 + 1
>
> meaning that the script should have a MAXIMUM of 3 threads.
>
> This might should a little limiting. However, it is important to note that
> this is mainly used to complement JMeter's HTTP Sampler. The Web Driver
> Sampler <https://jmeter-plugins.org/wiki/WebDriverSampler> is meant to be
> run in conjunction with a HTTP Sampler so that from the server's
> perspective, the load is production like. At the same time, the web sampler
> will simulate the user experience of interacting with the website/webapp
> whilst the server is under load, hence measuring the real user's experience
> at the same time.
>
> On Mon, Nov 13, 2017 at 11:34 PM, Bob Small <bo...@blackboard.com>
> wrote:
>
> > Well if you are using the GUI not much, I see limits of say 2000, if you
> > are command line you can use more, but again it does depend on your CPU.
> > If you have say an intel i5 likely you are going to run out maybe around
> > 10k, but it has many factors, network, app response, what calls you are
> > making etc. Play with it and test out to see where your system brakes
> > down. Also you can move to Blazemeter or AWS for more threads, and
> bigger
> > runs.
> >
> > Bob Small
> > QA Automation
> >
> > Development
> > Blackboard Transact
> >
> > T: 602.752.6301
> > blackboard.com/transact
> >
> >
> >
> > -----Original Message-----
> > From: Rajiv Nanduani [mailto:rajivkumarnandvani@gmail.com]
> > Sent: Monday, November 13, 2017 9:54 AM
> > To: user@jmeter.apache.org
> > Subject: how many threads we can run with webdriver sampler
> >
> > hi, i would like to know through jmeter using webdriver sampler how many
> > threads we can run as it says it depends on CPU core.
> >
> > thanks
> > This email and any attachments may contain confidential and proprietary
> > information of Blackboard that is for the sole use of the intended
> > recipient. If you are not the intended recipient, disclosure, copying,
> > re-distribution or other use of any of this information is strictly
> > prohibited. Please immediately notify the sender and delete this
> > transmission if you received this email in error.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> > For additional commands, e-mail: user-help@jmeter.apache.org
> >
>
>
>
> --
>
> Regards
>
> *RAJIV <http://testeverythingrajiv.com/> KUMAR
> <http://rajivkumarnandvani.wordpress.com/> NANDVANI
> <http://testeverythingqtp.blogspot.com>*
>
> http://rajivkumarnandvani.wordpress.com
> http://testeverythingqtp.blogspot.com/
>
Re: how many threads we can run with webdriver sampler
Posted by Rajiv Nanduani <ra...@gmail.com>.
thanks bob for the reply but i am surprised with this number like 2000 or
10k while it says if your CPU core like 4 processor than you can use upto 3
threads please see below references so i am confused now which is is
correct?
Meter allows the creation of multiple threads, and each thread is
responsible for creating load on the server. However, for the Web Driver
use case, the reader should be prudent in the number of threads they will
create as each thread will have a single browser instance associated with
it. Each browser consumes a significant amount of resources, and a limit
should be placed on how many browsers the reader should create. However,
the load testing cloud providers may help to scale WebDriver test up to
thousands of real browsers, look at BlazeMeter
<http://blazemeter.com/?utm_source=jmplinnerpages&utm_medium=cpc&utm_content=jmpininnerpgs&utm_campaign=WebDriverPlugin>
for
example.
From experience, the number of browser (threads) that the reader creates
should be limited by the following formula:
C = B + 1
where C = Number of Cores of the host running the test
and N = Number of Browser (threads).
eg, if the current reader's host has 4 cores, the formula would yield:
4 = 3 + 1
meaning that the script should have a MAXIMUM of 3 threads.
This might should a little limiting. However, it is important to note that
this is mainly used to complement JMeter's HTTP Sampler. The Web Driver
Sampler <https://jmeter-plugins.org/wiki/WebDriverSampler> is meant to be
run in conjunction with a HTTP Sampler so that from the server's
perspective, the load is production like. At the same time, the web sampler
will simulate the user experience of interacting with the website/webapp
whilst the server is under load, hence measuring the real user's experience
at the same time.
On Mon, Nov 13, 2017 at 11:34 PM, Bob Small <bo...@blackboard.com>
wrote:
> Well if you are using the GUI not much, I see limits of say 2000, if you
> are command line you can use more, but again it does depend on your CPU.
> If you have say an intel i5 likely you are going to run out maybe around
> 10k, but it has many factors, network, app response, what calls you are
> making etc. Play with it and test out to see where your system brakes
> down. Also you can move to Blazemeter or AWS for more threads, and bigger
> runs.
>
> Bob Small
> QA Automation
>
> Development
> Blackboard Transact
>
> T: 602.752.6301
> blackboard.com/transact
>
>
>
> -----Original Message-----
> From: Rajiv Nanduani [mailto:rajivkumarnandvani@gmail.com]
> Sent: Monday, November 13, 2017 9:54 AM
> To: user@jmeter.apache.org
> Subject: how many threads we can run with webdriver sampler
>
> hi, i would like to know through jmeter using webdriver sampler how many
> threads we can run as it says it depends on CPU core.
>
> thanks
> This email and any attachments may contain confidential and proprietary
> information of Blackboard that is for the sole use of the intended
> recipient. If you are not the intended recipient, disclosure, copying,
> re-distribution or other use of any of this information is strictly
> prohibited. Please immediately notify the sender and delete this
> transmission if you received this email in error.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> For additional commands, e-mail: user-help@jmeter.apache.org
>
--
Regards
*RAJIV <http://testeverythingrajiv.com/> KUMAR
<http://rajivkumarnandvani.wordpress.com/> NANDVANI
<http://testeverythingqtp.blogspot.com>*
http://rajivkumarnandvani.wordpress.com
http://testeverythingqtp.blogspot.com/
RE: how many threads we can run with webdriver sampler
Posted by Bob Small <bo...@blackboard.com>.
Well if you are using the GUI not much, I see limits of say 2000, if you are command line you can use more, but again it does depend on your CPU. If you have say an intel i5 likely you are going to run out maybe around 10k, but it has many factors, network, app response, what calls you are making etc. Play with it and test out to see where your system brakes down. Also you can move to Blazemeter or AWS for more threads, and bigger runs.
Bob Small
QA Automation
Development
Blackboard Transact
T: 602.752.6301
blackboard.com/transact
-----Original Message-----
From: Rajiv Nanduani [mailto:rajivkumarnandvani@gmail.com]
Sent: Monday, November 13, 2017 9:54 AM
To: user@jmeter.apache.org
Subject: how many threads we can run with webdriver sampler
hi, i would like to know through jmeter using webdriver sampler how many threads we can run as it says it depends on CPU core.
thanks
This email and any attachments may contain confidential and proprietary information of Blackboard that is for the sole use of the intended recipient. If you are not the intended recipient, disclosure, copying, re-distribution or other use of any of this information is strictly prohibited. Please immediately notify the sender and delete this transmission if you received this email in error.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
For additional commands, e-mail: user-help@jmeter.apache.org