I understood David's need is to control throughput, not to measure it -- that's exactly what the Constant Throughput Timer will do, but, as he says, only at the sampler level, not at the Job or Transaction level.

David: you can do this by adding the Constant Throughput Timer to the first sampler in the job only.

Remember the value you enter in the Constant Throughput Timer is samples per minute PER THREAD.

Hope this helps.

--
Salut,

Jordi.

Ryszard Lach wrote:
On Tue, Sep 09, 2003 at 11:42:28AM -0400, [EMAIL PROTECTED] wrote:

sure.  I'd like to have a controller that encapsulates a bunch of jdbc
calls underneath it eg "submit job"

I'd then like to measure the throughput of how often the controller get's
executed - at the moment I get the throughput of all the jdbc calls that
are exectuted, right?  I'd like to know "how many jobs are submitted per
minute" even though to submit a job, multiple jdbc calls are made.

If this is not currently possible, believe it would be a useful enhancement
- any pointers on where I'd start to extend things to include this?


Why don't you include one lightweight sampler into your job with
separate listener attached to it? It will show what you need.

Richard.


-- Salut,

Jordi.


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to