+++ Trevor Warren [12/08/02 11:02 -0700]: <snip>
Initially, when the customers were few, the load was miniscule and Squid on the Gateway would doa lovely job. Of late....Squid has been less of a boon and more of a curse to my setup. the memory requirements/cpu hoggin is taking my system down with cpu usage averagin @ 90%......nd due to tremendous requests being bombared @ it, the queue just dramatically increases response times to the clients.
Ok, move squid to a box with lots of small disks. squid is limited in its throughput by disk io, so you toss a box with loads of ram and fast disks (lots of spindles 4 x 9GB SCSI is better than 1 x 40 GB IDE).
And if CPU time is still hogged, then move the box to a 2.2 kernel/FreeBSD
That apart....my Transparent Web Caching solution also implements ad-zapping......which i hav made spawd 15 sub threads for url re-directing under squid.
Nope, just use DNS for this. Ads rresolve to 127.0.0.1
Due to the huge boggin down of my server...i had to shut down caching.
Is there ny solution....????. Where hav i erred.?????. Should i setup caching on a box different to the billing server..????
Yup, move the billing server to another machine hat is accessibly only via a local CGI (I am asuming a database here). This machine should not be accessible directly from the internet.
Which ISP, BTW?
Devdas Bhagat