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 <[email protected]> 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:[email protected]] > Sent: Monday, November 13, 2017 9:54 AM > To: [email protected] > 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: [email protected] > For additional commands, e-mail: [email protected] > -- Regards *RAJIV <http://testeverythingrajiv.com/> KUMAR <http://rajivkumarnandvani.wordpress.com/> NANDVANI <http://testeverythingqtp.blogspot.com>* http://rajivkumarnandvani.wordpress.com http://testeverythingqtp.blogspot.com/
