On Wed, 2004/11/03 (MST), <nooshin.zand@intel.com> wrote:
> I am not sure if polygraph server is short in resources or proxy server.
> Here are the messages I got.
> 000.41| Client.cc:306: error: 32/64 (c59) failed to establish a
> connection
> 000.41| 10.10.10.10 failed to connect to 10.10.10.1:10000
> 000.42| Connection.cc:120: error: 64/127 (s24) Too many open files
>
> Can not see any error message in system log file.
It looks like polyclt ran out of filedescriptors during the first minute
of the test. This may imply that you have a very low number of
filedescritors or a very aggressive initial request rate. Are you using a
simple.pg or similar best-effort workload? If yes, you probably need to
tune your OS for more filedescriptors and rebuild Polygraph. When executed
with --verb_lvl 10, polyclt will report then number of available
descriptors (look for "FD" in the beginning of the console log).
If you are using a constant-request rate test, consider ramping up the
request rate slowly; give the testbench and the proxy at least a couple of
minutes to adjust to increasing load.
PolyMix and WebAxe workloads have examples on how to do that in PGL.
To rule out a proxy as a bottleneck, consider running a no-proxy
back-to-back test. In most cases, you should make sure that a no-proxy
test can sustain higher loads than a proxy test. Otherwise, you may be
measuring testbench bottleneck, not the cache.
HTH,
Alex.
This archive was generated by hypermail 2b29 : Mon Feb 06 2006 - 12:00:28 MST