RE: [squid-users] Squid tunning

Try this henrik help for kernel 2.2 and I think with no different in
kernel 2.4
http://squid.sourceforge.net/hno/linux-lfd.html

--
Regards
    =================================================================
   /  Seyyed Hamid Reza    /        WINDOWS FOR NOW  !!            /
  /  Hashemi Golpayegani  /  Linux for future , FreeBSD for ever  /
 /    Morva System Co.   / ------------------------------------- /
/  Network Administrator/ hamid@morva.net   ,   ICQ# : 42209876 /
================================================================ 
-----Original Message-----
From: patrice.valentin@itc.alstom.com
[mailto:patrice.valentin@itc.alstom.com] 
Sent: Tuesday, June 04, 2002 9:38 PM
To: squid-users@squid-cache.org
Cc: placouague@coheris.com
Subject: [squid-users] Squid tunning
Hi,
As I said in my first mail, I search for tunning for my system, but
after update my file-max parameter (from 4096 to 32768) and my inode-max
parameter (from 8192 to 131072) I still have thousands of the following
messages in my cache.log file :
2002/06/03 16:54:44| sslWriteServer: FD 935: write failure: (32) Broken
pipe. 2002/06/03 16:54:44| sslWriteServer: FD 138: write failure: (32)
Broken pipe. 2002/06/03 16:54:49| WARNING! Your cache is running out of
filedescriptors 2002/06/03 16:54:49| sslWriteServer: FD 915: write
failure: (32) Broken pipe.
This is my squid.conf :
cache_peer 10.3.2.8 parent 8080 0 no-query default cache_swap_high 80
cache_swap_high 85 cache_dir diskd /cache1 15000 16 256 cache_dir diskd
/cache2 15000 16 256 cache_access_log /var/log/squid/access.log
cache_log /var/log/squid/cache.log cache_store_log none
request_body_max_size 20 MB
refresh_pattern         ^ftp:           1440    20%     10080
refresh_pattern         ^gopher:        1440    0%      1440
refresh_pattern         .               0       20%     4320
reference_age 1 week
acl all src 0.0.0.0/0.0.0.0
acl manager proto cache_object
acl localhost src 127.0.0.1/255.255.255.255
acl SSL_ports port 443 563
acl Safe_ports port 80 21 443 563 70 210 1025-65535
acl Safe_ports port 280         # http-mgmt
acl Safe_ports port 488         # gss-http
acl Safe_ports port 591         # filemaker
acl Safe_ports port 777         # multiling http
acl CONNECT method CONNECT
http_access allow all
http_access allow localhost
http_access deny all
icp_access allow all
miss_access allow all
never_direct allow all
I have to say that the proxy server serves around 27000 users, in one
hand directly, in the other hand through site proxies (squid in many
cases !). The issue is that the users get very often the error page with
broken pipe and slow performances, so please could someone help me
before I'm going to be crazy !
Best regards
Patrice Valentin
----- Forwarded by Patrice VALENTIN/FR/ITC/ALSTOM on 04/06/2002 16:01
-----
 
                      Patrice VALENTIN
                                               To:
squid-users@squid-cache.org                                    
                      22/05/2002 10:56         cc:
                                               Subject: Squid tunning
 
Hi,
I curently run a squid-2.4.STABLE1-5 on a Redhat 7.0
My server is a Dell poweredge 2450 with two Raid 1 system disks (2x9GB)
and two separate disks for two different cache directories (2x18.6GB)
the CPU is a Pentium III 1Ghz with 512MB SDRAM. More than 27000 users
have access to the Internet through this proxy, with a 8Mb access to the
ISP. My problem is the folowing, my users have complaints with a small
message which occur several times The system returned:
(32) Broken pipe
An error condition occurred while writing to the network.
I read a mail exchange between Henrik Nordstrom and a squid user that
dealt with TCP connection and some stuff like this. So could someone
tell me hox to tune my Redhat to solve this issue.
Best regards
Patrice Valentin
CONFIDENTIALITE : Ce message et les éventuelles pièces attachées sont
confidentiels. Si vous n'êtes pas dans la liste des destinataires,
veuillez informer l'expéditeur immédiatement et ne pas divulguer le
contenu à une tierce personne, ne pas l'utiliser pour quelque raison que
ce soit, ne pas stocker ou copier l'information qu'il contient sur un
quelconque support.
CONFIDENTIALITY : This  e-mail  and  any attachments are confidential
and may be privileged. If  you are not a named recipient, please notify
the sender immediately and do not disclose the contents to another
person, use it for any purpose or store or copy the information in any
medium.