Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

For httperf with a wsesslog is there a way to repeat the activity in the script without wrapping it in a shell loop?

If I do httperf --wsesslog=20,0,foo.wsesslog I get 20 sessions that run through the script in the file. Is there a way I can have 20 sessions that run through the script X times?

share|improve this question
--num-calls seems to be ignored... – Kyle Brandt Sep 17 '10 at 18:50
up vote 2 down vote accepted

Per your comment: The source says that the first argument of --wsesslog overrides --num-calls. That makes sense. I'm not seeing the wsesslog generator source making any reference to the --num-calls parameter.

I don't see the program doing what you're looking for without modifications. The wsesslog generator exits when the number of session is generates is equal or greater to the first parameter of the wsesslog argument (with the exit signaled through a global variable... ewww!).

You're best off just wrapping it in a shell. While, in theory, you could probably hack a parameter onto the wsesslog argument and just execute core_loop() that many times. The core_loop() function isn't idempotent, though, so it's probably not that simple.

share|improve this answer
"No" doesn't get more thorough than this :-) – Kyle Brandt Sep 24 '10 at 13:23

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.