Hi there,
I guess replying to Jens e-mail at 3am was not a very good idea.
Here is what I should have added to my original response. The examples
below are for the "first draft" tests, but they may help you to get
started.
If you got the "simple.pg" test going (as described in the User
Manual), you already know that all you need to run is a pair of these
commands, probably in two shell windows:
client> src/polysrv --config workloads/simple.pg
client> src/polyclt --config workloads/simple.pg
Well, to see some output, you may what to increase the verbosity level:
client> src/polysrv --config workloads/simple.pg --verb_lvl 10
client> src/polyclt --config workloads/simple.pg --verb_lvl 10
After this is working and you have read the description of the console
output (available on the Web), run a PolyMix-2 test:
client> src/polysrv --config workloads/polymix-2.pg --verb_lvl 10 \
--cfg_dirs workloads/include
client> src/polyclt --config workloads/polymix-2.pg --verb_lvl 10 \
--cfg_dirs workloads/include
After that is working, you are ready to move the server to its own
machine (note that we were using the "client" host in the examples
above). You will need to adjust the list of IP addresses in polymix-2.pg
file as described in the User Manual on the Web. I will call the file
with modified IP addresses "my-pm2.pg".
server> src/polysrv --config workloads/my-pm2.pg --verb_lvl 10 \
--cfg_dirs workloads/include
client> src/polyclt --config workloads/my-pm2.pg --verb_lvl 10 \
--cfg_dirs workloads/include
All the examples above did not include proxy. They were so-called
"no-proxy" tests. When they are working, just tell the client to go
through a proxy, using the actual proxy IP address and port number:
server> src/polysrv --config workloads/my-pm2.pg --verb_lvl 10 \
--cfg_dirs workloads/include
client> src/polyclt --config workloads/my-pm2.pg --verb_lvl 10 \
--cfg_dirs workloads/include --proxy 10.0.1.10:8080
Now you should be getting traffic through your proxy. If you are using
transparent (TCP hijacking) proxy, you do not need to specify the
--proxy parameter, of course.
If you need to run client and server on multiple hosts, all you need to do is
to adjust IP addresses in my-pm2.pg accordingly and start multiple client and
server processes.
To adjust request rate and other workload parameters, read the
polymix-2.pg file and ask questions if something is not documented. Most
(all?) of the PGL objects that polymix-2.pg is using are described on
the Web.
To get high request rates, you will need to remove "open_conn_lmt" limit
in your Robot definition(s) OR, better, create many robots using IP
aliases (one robot per alias). Check out "aka" tool if you are creating
a lot of aliases.
To get more statistics than console output, use the "--log" option and
then run something like
host> src/lx /tmp/logfilename.log
The latter will give you a very detailed output. Checkout lx's "--trace"
option if you want traces like the ones we used for the DataComm report.
To compare your results with what others might be getting, buy their products
and/or read the IRCache reports for the previous tests.
Again, please read past IRCache reports (see Results page on Poly Web site),
and if something is not clear, please ask specific questions.
Alex.
P.S. My apologies if the above commands contain typos. The User Manual
has actually tested examples (for the earlier Polygraph version).
This archive was generated by hypermail 2b29 : Tue Jul 10 2001 - 12:00:09 MDT