[squid-users] Squid on FC6, connections sitting around too long

2007-10-12 Thread Tory M Blue
Trying to figure out how I can reduce connections, sitting around on
my Squid boxes.

I'm still running with both Netcaches and a few Squid boxes and what
I'm seeing in my loadbalancer is that the Netcaches have 50% less
connections at any given time than the Squid boxes. Also the Netcache
(Netapp) is pushing more traffic, so what I'm gathering is that the
Netapp is taking in connections and releasing them faster than the
squid boxes.

I'm wondering if A) how I can diagnose this B), is there Squid
specific settings to handle  this (I don't really want to close an
active connection, but absolutely want a connection that has been left
by a client to go away).

Not sure if I should be looking at kernel/network tweaks or something
in my Squid configuration.

Packets Bits Packets Bits Current Max Total
18.5M   21.5G 23.6M 172.0G 7371.3K 1.2M  Squid
21.2M   26.8G 28.8M 199.2G 2741.3K 1.2M  NetCache
21.6M   27.1G 29.5M 206.4G 2491.3K 1.2M  NetCache
18.6M   21.6G 23.7M 172.5G 7351.2K 1.2M  Squid

Shows that the Squid boxes even though the loadbalancer is handing
connections off in a round robin fashion, Squid twice the connection
count as the Netapps.

What pertinent information would you need to throw an idea over?

Thanks
Tory


Re: [squid-users] Squid on FC6, connections sitting around too long

2007-10-12 Thread Adrian Chadd
You of course need to start looking at this by analysing what is actually
going on with the boxes and the network layer. There's not much that can be
suggested given the current information.

That said, NetCache's -are- much more efficient for most workloads than
Squid. Its just what happens when you sink $0 versus $LARGE into a product.




Adrian

On Fri, Oct 12, 2007, Tory M Blue wrote:
> Trying to figure out how I can reduce connections, sitting around on
> my Squid boxes.
> 
> I'm still running with both Netcaches and a few Squid boxes and what
> I'm seeing in my loadbalancer is that the Netcaches have 50% less
> connections at any given time than the Squid boxes. Also the Netcache
> (Netapp) is pushing more traffic, so what I'm gathering is that the
> Netapp is taking in connections and releasing them faster than the
> squid boxes.
> 
> I'm wondering if A) how I can diagnose this B), is there Squid
> specific settings to handle  this (I don't really want to close an
> active connection, but absolutely want a connection that has been left
> by a client to go away).
> 
> Not sure if I should be looking at kernel/network tweaks or something
> in my Squid configuration.
> 
> Packets Bits Packets Bits Current Max Total
> 18.5M   21.5G 23.6M 172.0G 7371.3K 1.2M  Squid
> 21.2M   26.8G 28.8M 199.2G 2741.3K 1.2M  NetCache
> 21.6M   27.1G 29.5M 206.4G 2491.3K 1.2M  NetCache
> 18.6M   21.6G 23.7M 172.5G 7351.2K 1.2M  Squid
> 
> Shows that the Squid boxes even though the loadbalancer is handing
> connections off in a round robin fashion, Squid twice the connection
> count as the Netapps.
> 
> What pertinent information would you need to throw an idea over?
> 
> Thanks
> Tory

-- 
- Xenion - http://www.xenion.com.au/ - VPS Hosting - Commercial Squid Support -
- $25/pm entry-level bandwidth-capped VPSes available in WA -


Re: [squid-users] Squid on FC6, connections sitting around too long

2007-10-15 Thread Henrik Nordstrom
On fre, 2007-10-12 at 10:52 -0700, Tory M Blue wrote:
> Trying to figure out how I can reduce connections, sitting around on
> my Squid boxes.
> 
> I'm still running with both Netcaches and a few Squid boxes and what
> I'm seeing in my loadbalancer is that the Netcaches have 50% less
> connections at any given time than the Squid boxes. Also the Netcache
> (Netapp) is pushing more traffic, so what I'm gathering is that the
> Netapp is taking in connections and releasing them faster than the
> squid boxes.

Probably you have a TCP connection based load balancer instead of one
that balances on actual traffic, and the Netcaches have persistent
connections disabled..

> I'm wondering if A) how I can diagnose this B), is there Squid
> specific settings to handle  this (I don't really want to close an
> active connection, but absolutely want a connection that has been left
> by a client to go away).

See the client_persistent_connections and persistent_request_timeout
directives.

Regards
Henrik


signature.asc
Description: This is a digitally signed message part


Re: [squid-users] Squid on FC6, connections sitting around too long

2007-10-16 Thread Tory M Blue
On 10/15/07, Henrik Nordstrom <[EMAIL PROTECTED]> wrote:
>
> Probably you have a TCP connection based load balancer instead of one
> that balances on actual traffic, and the Netcaches have persistent
> connections disabled..

> See the client_persistent_connections and persistent_request_timeout
> directives.
>
> Regards
> Henrik


For some reason when I initially configured these I thought
persistence was off by default, but looking at the config guides, I
see it's defaulted to on.

Playing with persistence on/off and persistence timeout is helping
things tremendously.

Squid is showing more output/input than the netcaches now. Now I'm
working on finding the right combination to keep open connections to a
minimum while continuing max throughput.

Client persistence in a reverse proxy environment makes no sens, and
since my server environment is also load balanced, not sure it makes
much sense there (still testing), but definitely persistence timeout
plays a big role.

Thanks again
Toryi


Re: [squid-users] Squid on FC6, connections sitting around too long

2007-10-16 Thread Henrik Nordstrom
On tis, 2007-10-16 at 09:42 -0700, Tory M Blue wrote:

> Client persistence in a reverse proxy environment makes no sens

I disagree. The TCP setup cost is a very large portion of the total page
load time, especially if you have users far away..

but it do place a different workload on the load balancers, and mixing
servers with different persistent connections settings the same farm is
hard to balance right..


Regards
Henrik


signature.asc
Description: This is a digitally signed message part