hello we are using squid just for proxy not for catching. we have 4 linux machines (vps) with the following specification and need to add 6 other machines to be 10 machines use squid. specification for each machine: ram = 1 GB port = 1 Gbps cpu = Intel(R) Xeon(R) CPU E5620 @ 2.40GHz, 2 cores os = CentOS Linux 5.8 hard disk space = 30 GB ---------------------------------------- we have configured for https proxy on port 9090 in this 4 linux machines the problem is that when the number of users raise the speed of proxy comes down and sometimes it does not connect.and the speed of loading pages is too slow. we compared the squid with the ccproxy on microsoft windows and understood that the ccproxy can support more users than squid in the same specification machine. we think we have some problem in configuring squid. we want to help us to improve the speed of the squid. here is the configuration of the squid. if you need vps user pass for monitoring and more information please say to email the user pass and ip of the vps. we installed the squid with the following commands ./configure --prefix=/usr/local/squid make all make install the squid version is squid-3.1.19 ------------------------------------------------------------------ cache deny all # # Recommended minimum configuration: # auth_param basic program /usr/local/squid/libexec/squid_db_auth --user squid_user --password c.0.m.p.u.t.e.r==(68)==)( --plaintext --persist acl manager proto cache_object acl localhost src 127.0.0.1/32 ::1 acl to_localhost dst 127.0.0.0/8 0.0.0.0/32 ::1 # Example rule allowing access from your local networks. # Adapt to list your (internal) IP networks from where browsing # should be allowed acl localnet src 10.0.0.0/8 # RFC1918 possible internal network acl localnet src 172.16.0.0/12 # RFC1918 possible internal network acl localnet src 192.168.0.0/16 # RFC1918 possible internal network acl localnet src fc00::/7 # RFC 4193 local private network range acl localnet src fe80::/10 # RFC 4291 link-local (directly plugged) machines acl SSL_ports port 443 acl Safe_ports port 80 # http acl Safe_ports port 21 # ftp acl Safe_ports port 443 # https 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 acl user_pass_auth proxy_auth REQUIRED # replace 10.0.0.1 with your webserver IP # # Recommended minimum Access Permission configuration: # # Only allow cachemgr access from localhost http_access allow manager localhost http_access deny manager # Deny requests to certain unsafe ports http_access deny !Safe_ports # Deny CONNECT to other than secure SSL ports http_access allow localnet # We strongly recommend the following be uncommented to protect innocent # web applications running on the proxy server who think the only # one who can access services on "localhost" is a local user #http_access deny to_localhost # # INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS # # Example rule allowing access from your local networks. # Adapt localnet in the ACL section to list your (internal) IP networks # from where browsing should be allowed http_access allow localhost http_access allow user_pass_auth http_access allow all # And finally deny all other access to this proxy # Squid normally listens to port 3128 http_port 9090 # Uncomment and adjust the following to add a disk cache directory. #cache_dir ufs /usr/local/squid/var/cache 100 16 256 # Leave coredumps in the first cache dir coredump_dir /usr/local/squid/var/cache # Add any of your own refresh_pattern entries above these. refresh_pattern ^ftp: 1440 20% 10080 refresh_pattern ^gopher: 1440 0% 1440 refresh_pattern -i (/cgi-bin/|\?) 0 0% 0 refresh_pattern . 0 20% 4320 cache_effective_user squid cache_effective_group squid cache_mem 600 MB
