I had a similar case once .... where i was extremely interesting on squid delay_pool functionality but didnt want to waste CPU and I/O because of squid.
I then installed squid with a NULL cache_dir, which means no cache at all being done. On the very few days i got logging just to check everything was OK. Some days after, i disabled logging as well.
http_access ACLs were pretty simple so i dont think they would waste too much cpu power.
Maybe disabling cache and logging you can use squid to acchieve your bandwidth limitation with some GREAT and FLEXIBLE ACLs, which i dont think you'll be able to acchieve with others solutions ..... and because of disabled features, maybe your CPU and I/O overhead wouldnt be that big .....
Umut Arus escreveu:
Thank for reply. But squid can not handle this type of limitations and waste excessive cpu. We removed that configuration before.
-- Atenciosamente / Sincerily, Leonardo Rodrigues Solutti Tecnologia http://www.solutti.com.br Minha armadilha de SPAM, NÃO mandem email gertrudes@xxxxxxxxxxxxxx My SPAMTRAP, do not email it
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
