On Tue, 12 Jun 2001, Joseph Mack wrote:
> In the meantime, how can I start 256 clients, rather than the 1024
> I'm starting now?
The number of robots is equal to the number of ClientR.addresses.
As you can see, the latter is calculated using robotAddrs() call.
http://www.web-polygraph.org/docs/reference/pgl/calls.html#call:docs/reference/pgl/calls/proxyAddrs
http://www.web-polygraph.org/docs/reference/pgl/types.html#type:docs/reference/pgl/types/AddrScheme
Most addressing schemes, including asWebAxe4 you are using, derive the
number of robots from the bench configuration in a natural way. For
example,
client_side.max_host_load = 700/sec;
client_side.max_agent_load = 0.7/sec;
settings yield 1000 robots per host. The number of hosts, in turn,
will depend on your peak_req_rate setting in a natural way:
ceil(peak_req_rate/client_side.max_host_load)
So, to get 256 robots, you can set peak_req_rate to
peak_req_rate = client_side.max_agent_load * 256;
This way you preserve the per-robot load levels which is a good thing.
There are other ways to achieve the same effect, of course.
Usually, we try to think in terms of request rates, not the number of
robots because per-robot rates may differ from one workload to
another. For example, we would say "700 req/sec is killing this box,
lets try 400 req/sec now":
TheBench.peak_req_rate = 400/sec;
... and Polygraph will create appropriate number of aliases. If you
have to create aliases by hand, you may find aka and tools/*ips.pl
scripts useful. We used those when Polygraph could not create aliases
on its own.
Alex.
This archive was generated by hypermail 2b29 : Tue Jul 10 2001 - 12:00:19 MDT