Ivan . wrote:
thanks
What am I looking for is something more along these lines.
http://www.webperformanceinc.com/library/files/proxy_server_performance.pdf
cheers
Ivan
Oh.
That paper describes requirements for a lab test. The good test
software; polygraph etc, have not changed AFAIK so go with those
mentioned if you want to.
What your initial email seemed to describe was for monitoring live
production installation performance.
Be aware these are very different. Throwing lab data at a production
server to a real remote web service is a very quick way to get yourself
a huge bandwidth bill and annoyed phone calls.
Amos
On Sun, May 2, 2010 at 12:04 PM, Amos Jeffries <squid3@xxxxxxxxxxxxx> wrote:
Ivan . wrote:
Hi
I recently implemented a new proxy system. I am looking at doing is
setting a periodical test that
goes out to the Internet, pull some content down and record the
relevant metrics.
PC------------>Proxy----------->FW------------------>Internet---------------->Site-with-content
Some sort of scheduled process on a PC, that pulls down some static
content from the same website, which is repeatable. The application
would then record metrics such as speed, time taken to download the
static content and log that.
Squid native access.log contains transfer duration and size metrics.
Some other options not in the default format provide additional metrics if
you need them.
See http://www.squid-cache.org/Doc/config/logformat/ for a lit of log
metrics.
Otherwise the SNMP counters can be used, but they do not go down as fine
grained as indvidual requests.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE9 or 3.1.1
--
Please be using
Current Stable Squid 2.7.STABLE9 or 3.1.1
