How to test browser side performance with 500 concurrent users through jmeter?

[Nupur Talwar]

Hi ,

I have another problem in hand. I need to test performance of the application with 500 concurrent users. The challenge now is that this I have to test for browser side. I have integrated my selenium script but as the challenge I can produce more than 25 users for the execution. 

Is there any browser less technique with Jmeter (any plugin) that can help me achieve this Browser side performance testing for 500 concurrent threads?

Thanks,

Nupur

[Cheen-Pin Lim]

With 500 users it sounds like you are trying to do a load test on your server. Would the JMeter HTTP sampler be a better choice for your needs? Or am I missing something?

--
You received this message because you are subscribed to the Google Groups "jmeter-plugins" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jmeter-plugin...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Nupur Talwar]

Actually this is the challenge. I have to load test client side with around 500 users. Can it be possible? also does using htmunit driver can be a good choice for this??

[vdab...@gmail.com]

Hi,

If you want to simulate 500 virtual users.

I have to choose the htlmunit driver and you need at least 2 computers for JMeter Load Injector (JMeter started in server mode) and 1 machine for the JMeter controler ( => 3 computers or servers).

Of course, you must add some timers with realist wait time between different pages (Webdriver samplers) (like > 1minute to fill a complex form).

and few Listeners but write results in a .csv file to analyse result after the load test.


Regards
Vincent D.

[gli...@gmail.com]

JMeter can do pretty much to pretend a real browser so it should be no difference for application whether it is being hit by 500 browsers or by 1-2 JMeter instances. 

Consider following JMeter elements present and enabled:

• HTTP Cookie Manager - to represent browser cookies, enable cookie-based login functionality and distinguish sessions
• HTTP Header Manager - to simulate HTTP headers being sent by browser, especially User-Agent one
• HTTP Cache Manager - to simulate browser cache
• HTTP Request Defaults - to set following configuration for all requests
• Check "Retrieve All Embedded Resources" to allow JMeter downloading images, css, scripts
  
• Check "Use concurrent pool"
• Set size to 2-4 threads 

Following above recommendations you should be able to perform browser-like testing using JMeter. 

Hope this helps,

D.