From: Michele Petrazzo - Unipex srl <michele.petrazzo@unipex.it>
To: netfilter@vger.kernel.org
Subject: Iptables execution time
Date: Thu, 16 Oct 2008 19:29:51 +0200 [thread overview]
Message-ID: <48F77A0F.1050405@unipex.it> (raw)
Hi list,
I'm seeing that the execution of an iptables update via a shell script
take very different time into a my "in production" server and on my test
server. My script has about 1500 iptables commands and simple insert a
rule on a table.
On my in production server, it takes about 45 sec and on my test server 4!
My server are 2x Xeon 2.6GHz (so 4 cpus) with 2.6.26 on x86_64 SMP with
2GB ram and my test server amd 3000+ with 2.6.26 i686 1GB,
Can be that, on the production server that has a lot of connection it
take so lot of time due the connections (I try to say that it has to "lock"
the kernel before and "unlock" after an iptables add) or there can be some
problems?
Thanks,
Michele
P.s. Yes, I know that the same rules with iptables-restore on my test
server takes about 0.5 sec :)
next reply other threads:[~2008-10-16 17:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 17:29 Michele Petrazzo - Unipex srl [this message]
2008-10-16 17:48 ` Iptables execution time Pablo Neira Ayuso
2008-10-16 18:17 ` Michele Petrazzo - Unipex srl
[not found] ` <002301c92fe5$3234ff00$969efd00$@bourke@mobileinternet.com>
2008-10-17 11:53 ` Pablo Neira Ayuso
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=48F77A0F.1050405@unipex.it \
--to=michele.petrazzo@unipex.it \
--cc=netfilter@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.