Alex Rousskov wrote:
> > In the meantime, how can I start 256 clients, rather than the 1024
> So, to get 256 robots, you can set peak_req_rate to
> peak_req_rate = client_side.max_agent_load * 256;
256 is replacing count(client_side.hosts) which in my example =1.
polyclt exits straight away saying something like "too many clients".
If I put 0.5 instead of 256, I get the client to fire up.
> If you
> have to create aliases by hand, you may find aka and tools/*ips.pl
> scripts useful.
ifconfig lo:0 10.1.0.0/16
works so far.
>>
>.> > If it's the per-process limit being hit, you will have to change your
>> > ulimits.
>>
>> put these at 8192 without anyeffect on the polyclt numbers reported above.
> Make sure you re-configure and re-compile Polygraph when you change FD
> limits.
No change. The code has code like
Min(FD_SETSIZE, rlimit) (eg in PolyApp.cc) which picks up 1024. I haven't
found where it picks up rlimit yet (there are no likely suspects in the header
files in PolyApp.c).
> Polygraph reports the number of FD it can open during ./configure. It
> also reports the number of FD available at start up. Again, I do not
> know how to change the number of FDs on Linux (including the
> FD_SETSIZE value), but there is a way (and it is probably Linux
> version specific).
It says 1024. Will have to find where it's picking it up. In the meantime I
can live with 256 clients.
>As virtually everything else, these addresses come from your
>configuration file:
> server_side.addr_mask = '192.168.1.0:8080';
> vipMap.addresses = serverAddrs(asWebAxe4, TheBench);
> vipMap.names = addresses;
> ClientR.origins = vipMap.names;
>
>Since asWebAxe4 is returning aliases based on addr_mask, you
>probably want to replace the second line with
> vipMap.addresses = server_side.hosts;
I get "server_side.hosts or its components not declared"
when I try to run the client.
I still don't see how I get the servers listening on 192.168.128.1:8080
when I put
server_side.addr_mask = '192.168.1.0:8080';
The servers listen on the same address if I have the address_mask 192.168.255.255
or 192.168.0.0. It appears that the server_side.addr_mask isn't affecting the
address the server is listening to.
> Meanwhile,
> please use the comments above. A useful rule of thumb is that
> Polygraph knows and does only what you tell it via PGL. There is
> virtually no magic going on. Try to understand PGL files you use
> (AFAIK, all object types/fields are documented). It will help you
> long-term.
sure. I'm just starting. I'll get more dexterous as I go. I'm just trying
to get the default configuration working right now to see if the L4 box
I have fits your setup.
Thanks Joe
-- Joseph Mack PhD, Senior Systems Engineer, Lockheed Martin contractor to the National Environmental Supercomputer Center, mailto:mack.joseph@epa.gov ph# 919-541-0007, RTP, NC, USA
This archive was generated by hypermail 2b29 : Tue Jul 10 2001 - 12:00:19 MDT