Alternative of distributed load testing

What is your bottleneck?

1. JMeter needs to be properly tuned for high loads, make sure to follow JMeter Best Practices and recommendations from 9 Easy Solutions for a JMeter Load Test “Out of Memory” Failure article.

2. Your operating system needs to be tuned as well in particular:

   • enable tcp_tw_reuse
   • decrease tcp_fin_timeout
   • increase ip_local_port_range

3. If you're still hitting CPU or RAM limits consider using i.e. Tsung which is known for producing higher throughput from the same hardware. But be aware that you won't be able to create more than 65535 because this is the maximum number of TCP ports

Why not take an alternative path. You can find ~80% of all performance defects with a single user.

• Turn on time-taken in your HTTP access logs

• Use a profiler model to collect response times during unit, manual, and automated functional testing.

• Find and address the highest resource use items

• Where a page is running long, address the rendering or data storage (i.e. missing index) that is driving a page response time to slow.

If you have an existing version of the application in production, even better.

If you genuinely have 32000 consistent concurrent users on your host, the amount of risk of failure is so substantial that even the most expensive tools on the market pale in comparison to an outage risk. your demand of free is at odds with the risk and the value of the mitigated risk.