Mehdi Sarmadi wrote > Hey > > Alright. About refresh pattern you have a very excessive list IMHO. I > don't know about your hardware but generally for a typical general purpose > SMB server hardware, that's too much. If you want to stick with it and > can't reduce the list. > Check, how many core's you machine have. You should know squid naturally > sticks . A solution is to start multiple squid instances, that way you can > have squid(refresh_pattern) load distributed on more than one CPU core, > thus you'll get better performance. > > Hope it helps > Cheers Thanks for the tip . It has a core i3 cpu so it has 4 cores . Unfortunately squid does not load fine across all cores specially in older versions like mine v 3.1 . Multi instance has its own complexity and headaches . i am trying to have clean design to be away from those problems . It was very useful if squid could do the refresh_pattern jobs by other cores . or some trick like that . -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/High-cpu-usage-by-re-search-internal-tp4667550p4667658.html Sent from the Squid - Users mailing list archive at Nabble.com. _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
