From: "Leonardo Rodrigues Magalhães" <leolistas@solutti.com.br>
To: Umut Arus <umuta@sabanciuniv.edu>
Cc: netfilter ML <netfilter@vger.kernel.org>
Subject: Re: Limiting httpd traffic
Date: Sat, 05 Jan 2008 11:39:20 -0200 [thread overview]
Message-ID: <477F8888.3000202@solutti.com.br> (raw)
In-Reply-To: <20080105153519.yw3oill1e7pc80gk@webmail.sabanciuniv.edu>
[-- Attachment #1: Type: text/plain, Size: 1165 bytes --]
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@solutti.com.br
My SPAMTRAP, do not email it
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 5589 bytes --]
prev parent reply other threads:[~2008-01-05 13:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-05 0:25 Limiting httpd traffic Umut Arus
2008-01-05 11:32 ` G.W. Haywood
2008-01-05 11:50 ` Umut Arus
2008-01-05 11:57 ` G.W. Haywood
2008-01-05 13:19 ` Leonardo Rodrigues Magalhães
2008-01-05 13:35 ` Umut Arus
2008-01-05 13:39 ` Leonardo Rodrigues Magalhães [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=477F8888.3000202@solutti.com.br \
--to=leolistas@solutti.com.br \
--cc=netfilter@vger.kernel.org \
--cc=umuta@sabanciuniv.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox