Re: [squid-users] throughput limitation from cache

From: Peter Smith <peter.smith@dont-contact.us>
Date: Thu, 19 Jan 2006 15:10:05 -0600

Richard, I was wondering if you've gotten anywhere with this? I did
some testing on my fairly busy squid cache.. Here are the results, from
Squid's perspective (access.log)..

stimeA 47639 clientA TCP_MISS/200 49075472 GET
http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.14.tar.gz -
DIRECT/204.152.191.5 application/x-gzip
stimeB 50438 clientA TCP_HIT/200 49075479 GET
http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.14.tar.gz - NONE/-
application/x-gzip
stimeC 44111 clientA TCP_HIT/200 49075480 GET
http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.14.tar.gz - NONE/-
application/x-gzip
stimeD 39758 clientA TCP_HIT/200 49075480 GET
http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.14.tar.gz - NONE/-
application/x-gzip

stime is basically the Squid server's system time. If I take the 2nd
ulong value, or the request length (490754XX) and divide that by the
first ulong value, or the service time (in MS, XXXXX), I get the
following rates.

stimeA 1030153 B/s
stimeB 972986 B/s
stimeC 1112545 B/s
stimeD 1234354 B/s

What do you see on your system(s) ?

I was using the following client command as a test...

http_proxy=http://proxy:3128 wget
http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.14.tar.gz -O- >
/dev/null

After you have it cached on the proxy, you might try this *on* the proxy
itself.

http_proxy=http://localhost:3128 wget
http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.14.tar.gz -O- >
/dev/null

Peter
Received on Thu Jan 19 2006 - 14:10:16 MST

This archive was generated by hypermail pre-2.1.9 : Wed Feb 01 2006 - 12:00:01 MST