From: Tihomir Katic <tihomir.katic@gmail.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [NEW SOFTWARE] FIRO - Iptables optimization
Date: Thu, 9 Jun 2011 16:23:15 +0200 [thread overview]
Message-ID: <BANLkTikkY=Hcksw7Lb8CvgD+fhDN=TtCJg@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.01.1106091615510.31505@frira.zrqbmnf.qr>
>That is purely noise. You need a lot more rules (10000 and up) to
>measure an effect.
I've been testing, list with 1000 rules, list with 10000 rules, list
with 50000 rules.
Searching for minimum time, in 100 tests, etc.
1 MIN ( 1000 single): 0.206000 us
1 MIN (1000 array): 0.264000 us
1 MIN (10000 single): 0.081400 us
1 MIN (10000 array): 0.156900 us
I couldn't restore 50000 array command (memory issue) on Iptables 1.4.4
But it can be restored on 1.2.9 (don't have right now results for that)
Br
2011/6/9 Jan Engelhardt <jengelh@medozas.de>:
> On Thursday 2011-06-09 16:07, Tihomir Katic wrote:
>>
>>Also, I have been doing some tests, and in config.txt you will see:
>>## Optimal size of multiport - port array
>>port_array_size_optimal = 10
>>
>>It means, it will merge 2 rules for example --dport 1:5 and --dport
>>21:25 into -m multiport --dports 1,2,3,4,5,21,22,23,24,25
>
> This should be -m multiport --dports 1:5,21:25
>
>>But, based on my recent tests, it should be
>>port_array_size_optimal = 15
>
> Yes, multiport can hold 15 "things".
>
>>rule with --dport 1:5 takes e.g. ~0.2 us
>>and rule with 15 elements in multiport array lasts ~0.4us, so it is
>>pretty much the same
>
> That is purely noise. You need a lot more rules (10000 and up) to
> measure an effect.
>
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-06-09 14:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 13:18 [NEW SOFTWARE] FIRO - Iptables optimization Tihomir Katic
2011-06-09 13:23 ` Patrick McHardy
2011-06-09 13:33 ` Pierre Chifflier
2011-06-09 13:39 ` Tihomir Katic
2011-06-09 13:44 ` Jan Engelhardt
2011-06-09 14:07 ` Tihomir Katic
2011-06-09 14:16 ` Jan Engelhardt
2011-06-09 14:23 ` Tihomir Katic [this message]
2011-06-09 14:25 ` Tihomir Katic
2011-06-09 14:34 ` Jan Engelhardt
2011-06-09 15:55 ` Tihomir Katic
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='BANLkTikkY=Hcksw7Lb8CvgD+fhDN=TtCJg@mail.gmail.com' \
--to=tihomir.katic@gmail.com \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).