[httperf] Stressing Tomcat with httperf - concurrency issue
martin.arlitt at hp.com
Mon Jul 20 05:36:10 PDT 2009
Httperf is event-based (and single-threaded). If you want you could start multiple instances of httperf (one per core on your client, or use multiple clients). You may want to specify the option -client=I/N (where N is the number of httperf processes you started, and I is the identifier for the process (between 0 and N-1). Please note that -client option does not start multiple instances, it is used by some of the workload generation parameters to ensure the workloads generated are not identical across httperf processes.
From: httperf-bounces at napali.hpl.hp.com [mailto:httperf-bounces at napali.hpl.hp.com] On Behalf Of Barak Yaish
Sent: Monday, July 20, 2009 2:23 AM
To: httperf at napali.hpl.hp.com
Subject: [httperf] Stressing Tomcat with httperf - concurrency issue
I'm using httperf in order to load a Tomcat deployed with my applications. The requests do arrive to the server and processed, but according to the log files (log4j), its always the same thread that processes the requests, which probably means that httperf doesn't truly creates concurrency. These are the parameters I'm using:
httperf --wsess=10,5,5 --num-conns=4 --burst-length=4 --rate=0 --timeout=5 --server="server_ip" --uri="/path/to?params"
Can some assist with the correct configuration so the requests will hit the tomcat in parallel?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the httperf