Here are my compile time options:
./configure --enable-storeio=diskd,null --enable-snmp --enable-devpoll
On 10/5/07, Frank Ruiz <frank.ruiz@xxxxxxxxx> wrote:
> I have 2 squid instances.
>
> Both are taking the same amount of connections, and both are
> connecting to the same exact pool of origins via a lb.
>
> 2344 root 13G 13G cpu1 0 0 4:03:10 25% squid/1
> 2096 root 13G 13G sleep 31 0 4:47:22 9.2% squid/1
>
>
> After about 14 hours of runtime, the instances hit 25% utilization,
> and then never seem to restabilize.
>
>
> This is all I see in my cache.log for the instance that is maxed out:
>
> 2007/10/05 10:47:25| clientReadRequest: FD 107 (82.38.189.46:5430)
> Invalid Request
> 2007/10/05 11:05:13| WARNING: unparseable HTTP header field
> {Accept-CharsetGET /pict/320155568274_1.jpg HTTP/1.1}
> 2007/10/05 11:06:55| parseHttpRequest: Unsupported method 'Connection:'
> 2007/10/05 11:06:55| clientReadRequest: FD 1808 (84.71.71.234:35312)
> Invalid Request
> 2007/10/05 11:06:55| parseHttpRequest: Unsupported method 'Connection:'
> 2007/10/05 11:06:55| clientReadRequest: FD 1007 (12.25.108.29:63647)
> Invalid Request
> 2007/10/05 11:22:01| parseHttpRequest: Unsupported method 'Connection:'
> 2007/10/05 11:22:01| clientReadRequest: FD 1612 (81.104.41.63:48329)
> Invalid Request
> 2007/10/05 11:22:01| parseHttpRequest: Unsupported method 'Connection:'
> 2007/10/05 11:22:01| clientReadRequest: FD 1685 (74.236.38.154:50482)
> Invalid Request
> 2007/10/05 11:22:06| parseHttpRequest: Unsupported method 'Connection:'
> 2007/10/05 11:22:06| clientReadRequest: FD 6278 (83.112.151.249:53849)
> Invalid Request
>
>
> The box is a 2 cpu dual core, so each squid instance maxes out at 25% cpu.
> The are strictly in memory cache (no disk), and they each have 9G of
> RAM per instance.
>
> Can someone give me an idea of what is happening?
>
> Thanks.
>
