Looked at documentation at jmeter saying java implementation of http request.
The API is best suited to single-threaded usage – various settings (e.g. proxy) are defined via system properties, and therefore apply to all connections.
This statement is confusing. Does this mean if you put 100 threads in ThreadGroup, you only have actually one java thread? Just one thread to multiple connections? Or it means something else.
I thought Jmeter is to creating multiple java threads for stress testing. We want to take advantage of multiple processors with multiple java threads for stress testing.
No, but I agree it’s confusing. 100 threads means up to 100 concurrent connections.
The documentation says that since the Java HTTP API is configured through system properties, it works best with single-threaded applications. In multi-threaded environment it’s hard to apply settings to only a single thread only because system properties are global.
HTTPClient sampler (which you should prefer) doesn’t have such limitations since everything is configured explicitly and on a connection basis.