Hello all,
I'm comming back with new info:
- i rebuilded from src.rpm and upgraded from squid-2.5.STABLE6-3.4E.11 to
squid-2.5.STABLE11-1.FC3!
After upgrade, no semnificative improvements regarding my problem (between
11AM up 15PM my squid become slower - connections are worse then a dial-up
connection)
- i recorded CPU Load, Free Memory, New TCP Connections, Established TCP
Connections via snmp.
CPU average=4% (with max 25%) so.... super fine!
Free Memory = 24M !!!!!! I have installed on my serverv 1G Reg Ecc available
(plus 2Gb swap). Swap still remain unused and from phisycal memory it remain
18-24M free.
Connection information for squid:
Number of clients accessing cache: 130
Number of HTTP requests received: 482956
Average HTTP requests per minute since start: 163.7
Select loop called: 4295056 times, 41.213 ms avg
Before to order more memory, i would like to know if there is something wrong
in my squid.conf.
# cat /etc/squid/squid.conf
http_port 3128
hierarchy_stoplist cgi-bin ?
acl QUERY urlpath_regex cgi-bin \?
no_cache deny QUERY
cache_mem 256 MB
maximum_object_size 32768 KB
maximum_object_size_in_memory 64 KB
cache_replacement_policy heap GDSF
memory_replacement_policy heap GDSF
cache_dir aufs /var/spool/squid 20480 16 256
cache_store_log none
ftp_user squid@mydoom.ro
auth_param basic children 100
auth_param basic realm Squid proxy-caching server
auth_param basic program /usr/lib/squid/pam_auth
auth_param basic credentialsttl 2 hours
auth_param basic casesensitive off
refresh_pattern ^ftp: 1440 20% 10080
refresh_pattern ^gopher: 1440 0% 1440
refresh_pattern . 0 20% 4320
half_closed_clients off
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 lanpass proxy_auth REQUIRED
acl to_localhost dst 127.0.0.0/8
acl SSL_ports port 443 563
acl Safe_ports port 80 # http
acl Safe_ports port 21 # ftp
acl Safe_ports port 443 563 # https, snews
acl Safe_ports port 70 # gopher
acl Safe_ports port 210 # wais
acl Safe_ports port 1025-65535 # unregistered ports
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 manager localhost
http_access deny manager
http_access deny !Safe_ports
http_access deny CONNECT !SSL_ports
http_access allow localhost
http_access allow lanpass
http_access deny all
http_reply_access allow all
icp_access allow all
cache_mgr admin@mydoom.ro
visible_hostname proxy.mydoom.ro
announce_period 0
log_icp_queries off
cachemgr_passwd *** all
buffered_logs on
coredump_dir /var/spool/squid
client_persistent_connections off
What is not mentioned above (in squid.conf) has default value!
Top say the same thing... see below results sorted by memory usage:
top - 10:03:14 up 2 days, 7:11, 3 users, load average: 0.36, 0.33, 0.29
Tasks: 171 total, 1 running, 170 sleeping, 0 stopped, 0 zombie
Cpu(s): 4.0% us, 4.5% sy, 0.0% ni, 89.4% id, 0.0% wa, 0.3% hi, 1.8% si
Mem: 1034680k total, 1014068k used, 20612k free, 68500k buffers
Swap: 2008084k total, 144k used, 2007940k free, 491916k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
4537 squid 15 0 453m 288m 1792 S 5.3 28.5 11:52.43 squid
4539 squid 17 0 30440 28m 676 S 0.0 2.8 0:06.38 pam_auth
2901 mysql 16 0 120m 18m 3480 S 0.0 1.8 0:00.11 mysqld
Any ideas?
Alex
On Saturday 24 September 2005 21:15, Matus UHLAR - fantomas wrote:
> > > Okay... These look pretty good. Hits are fast, misses are okay, DNS
> > > requests are about what I would expect... I'm a bit perplexed. What
> > > are the symptoms of slow connections? Is it throughput on large
> > > downloads, pages with lots of connections (msn.com with it's thousands
> > > of images), does it just take forever for a connection to get started,
> > > or is it something else entirely?
>
> On 24.09 15:21, Alex wrote:
> > NO, the situation is very simple: not matter content of page. Even if
> > www.google.com is accesed, it take more then 20-30s to load/display it
> > correctly. Without squid, www.google.com is loaded instantly!
>
> ehm, this might be caused by:
>
> 1. clients connect from IP's not in DNS, and your squid checks for their
> reverse (and probably direct) DNS informations
> 2. you are requiring ident for them, they are firewalled and don't support
> ident requests
>
> for 99% it's the first case. turn off dns checking in squid, or better, fix
> your internal DNS.
Received on Thu Oct 06 2005 - 01:04:14 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Nov 01 2005 - 12:00:04 MST