Hi, The limit really depends on your system and your test plan. If you follow JMeter Best-practices :
- http://jmeter.apache.org/usermanual/best-practices.html - http://www.ubik-ingenierie.com/blog/jmeter_performance_tuning_tips/ you can easily go to much more threads . For example we currently load without any problem more than 3500 threads with 1 JVM on a real life ecommerce website with 8 vCPU + 6 Go Xmx and there are reports of tests with more than 10K threads on a AWS m1.xlarge with a 64 bit processor, 4 virtual CPUs and 15 GB RAM. You can also use distributed testing if you want to go up. Finally if not enough there are a lot of Cloud offers (free and commercial) based on JMeter Regards @ubikloadpack On Mon, Dec 15, 2014 at 2:59 PM, Mark Lybarger <[email protected]> wrote: > > i'm looking to test a system that should handle a load of 100,000 clients > ... eventually. right now, the clients are in fact time shifted and really > the system supports 100 or so concurrent clients. that said, i'm looking > to do some load / performance testing, so i naturally look to jmeter. > > i've read several articles or blogs suggesting a limit of 300 threads for > jmeter testing. i'm going to need many many more. perhaps 3,000 would be a > good starting number. so, finally, my question is this. is the thread limit > based on system resources? would using a distributed jmeter allow me to > get up to 3,000 threads? > > what types of loads have jmeter users typically been able to put on their > systems? > > my system under test is a back office system, but it provides an http > interface to the end client. > > thanks! > -mark- > -- Regards Ubik Load Pack <http://ubikloadpack.com> Team Follow us on Twitter <http://twitter.com/ubikloadpack> Cordialement L'équipe Ubik Load Pack <http://ubikloadpack.com> Suivez-nous sur Twitter <http://twitter.com/ubikloadpack>
