|
<- Previous Message | Next Message -> Thread Index [isp-caching] Re: unusually high cpu load with squid
Hi! > look, with this out-of-the-box configs you'll not getting a fast > config, also you kernel lacks defenitly essential configuration for > performance tuning. what things in kernel could have such a great impact on squid's CPU usage??? > you should use in squid at least diskd instead of ufs you really think that ufs is causing that CPU load?? I'm gonna try diskd.. > this one also should be 256 or more > > cache_mem 64 MB tried, no result.. And, I tried to install FreeBSD on this machine - same thing, 60% cpu load with about 2Mbit/s of traffic. I am very upset. > On Wednesday 10 March 2004 01:27, thor@....sarkor.uz wrote: > > Thank you for your concern! > > > > Here is all non-comment lines of my squid.conf: > > > > tcp_outgoing_address XX.YY.ZZ.QQ > > hierarchy_stoplist cgi-bin ? > > acl QUERY urlpath_regex cgi-bin \? > > no_cache deny QUERY > > cache_mem 64 MB > > cache_swap_low 95 > > cache_swap_high 98 > > cache_dir ufs /var/spool/squid 10240 16 256 > > request_body_max_size 10 MB > > 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 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 Safe_ports port 901 # SWAT > > acl purge method PURGE > > acl CONNECT method CONNECT > > acl dialup src XX.YY.ZZ1.0/24 > > acl dialup src XX.YY.ZZ2.0/24 > > http_access allow manager localhost > > http_access deny manager > > http_access allow purge localhost > > http_access deny purge > > http_access deny !Safe_ports > > http_access deny CONNECT !SSL_ports > > http_access allow localhost > > http_access allow dialup > > http_access deny all > > icp_access allow all > > httpd_accel_port 80 > > httpd_accel_host virtual > > httpd_accel_with_proxy on > > httpd_accel_uses_host_header on > > > > Thanks again! > > > > Timur Irmatov. > > > > On Tue, Mar 09, 2004 at 07:32:12PM -0300, infomatik wrote: > > > Hi Timur > > > > > > this is Jo?o form Brazil at http://info.matik.com.br > > > > > > I am highly specialized in squid > > > > > > this indeed is not a normal behaviour but its hard to say because I do > > > not know you configurations > > > > > > your final decision using freebsd is clearly a wise one, use 4.9-Stable > > > to get a runner > > > > > > shure your system should be tuned for beeing a cache, don't forget it > > > > > > we get on machines with similar charge ~200 cache hits and max 10% cpu > > > load :) > > > > > > What are your squid.conf settings? > > > > > > Jo?o > > > > > > On Friday 05 March 2004 13:51, thor@....sarkor.uz wrote: > > > > Hi! > > > > > > > > > > > > I'm running squid as transparent proxy server for dial-up users. > > > > Everything seems to be ok except CPU load. With 1.5 Mbit/s (35 > > > > requests per second) traffic through proxy, squid consumes about 50-60% > > > > of cpu (from which 40-45% is system time). And with a load of 3-3.5 > > > > Mbit/s processor load comes to 90%. > > > > > > > > The server is single-processor Xeon 2.66 Mhz, 1Gb RAM, 36.6 Gb SCSI > > > > disks on AIC7902 controllers. OS is Debian Linux 3.0, kernel 2.4.24. > > > > > > > > Users are redirected to proxy by iptables nat rule. > > > > > > > > I have already asked this question in squid-users@... > > > > mailing list, and received no answer except confirmation that such > > > > behaviour is really unusual. > > > > > > > > 'half_closed_clients off' does not change anything.. > > > > > > > > I'm really desperate. If anybody have any ideas, I will be glad to > > > > experiment! Now the only thing I could try is to install FreeBSD > > > > instead of Debian/Linux and see, how it will perform. > > > > > > > > > > > > Sincerely Yours, > > > > Timur Irmatov. > > - -- > > ______________________________________________________ > > N?s implementamos asas na sua rede > http://info.matik.com.br > Tecnologia e Desenvolvimento > > (18)231.3670 9773.1053 ICQ 5135957 > > GPG Key http://info.matik.com.br/info.asc > { D5B0 B543 8B0F A35D 28D9 F2DD 375B 7088 0629 214A } > Aten??o: Msgs sem assinatura n?o s?o nossas. > Atention: Msgs without signature are not from us. > ______________________________________________________ > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.3 (GNU/Linux) > > iD8DBQFATt5xN1twiAYpIUoRArlyAKCqFjDW+BJvMuqtJBpEYjp9U0aNwgCgiP8n > 3/O7CQtnxkeOQzK92fGP/Nk= > =Elgq > -----END PGP SIGNATURE----- To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with. ------------------------ANNOUNCEMENT--------------------------------- --------------------------------------------------------------------- - ISPCON Spring 2004 - Washington DC Hilton & Towers - - The ISP and WISP event - www.ispcon.com - - Where the industry shares its formulas for success!. ---------------------------------------------------------------------- ----------------------------------------------------------------------
Thread Index |