>
> Given those cache sizes, your Squid box should be using around 110 MB
of RAM for index plus a little. Even assuming a worst-case of a minutes
traffic accumulated in transit buffers comes nowhere close to filling
16
> GB up.
>
> Some questions that may help narrow down where the slow is coming from:
> What version of Squid is this?
> What are your avg object size?
> How many concurrent client connections?
> "slow" and "normal" response speeds?
> Do you notice any change in the Squid->Internet request types during
> the slowdown? (ie a move to extra MISS/HIT/IMS/REFRESH)
>
> And like Michael said the disk IO stats are important to look at. When
the cache_dir gets to 94% full it will start spending CPU and disk
cycles on erasing objects. If it reaches 95% a larger portion of cycles
get used until it drops down below 94% again.
>
>
> Amos
_______________________________________________________________________
>
Hi Amos
Thanks a lot to all for the help.
I'm suspecting now that is a problem of I / O. The cache is on the same
disk that the system, I'll try to put it on a second disc or distributed
between two disks.
I followed exactly this tutorial (in Portuguese):
http://www.vivaolinux.com.br/artigo/Squid-+-Bridge-+-TProxy-no-CentOS-5.4/
Kernel: 2.6.30.10
Squid: 3.1.1
iptables: 1.4.3
All compiled from sources.
> How many concurrent client connections?
> "slow" and "normal" response speeds?
> Do you notice any change in the Squid->Internet request types during
> the slowdown? (ie a move to extra MISS/HIT/IMS/REFRESH)
How to I know those values ?
Thanks again.
roberto
Received on Fri Apr 15 2011 - 23:56:58 MDT
This archive was generated by hypermail 2.2.0 : Sat Apr 16 2011 - 12:00:04 MDT