From: Patrick McHardy <kaber@trash.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Harald Welte <laforge@netfilter.org>,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>,
Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Subject: Re: [RFC] ctnetlink events drop benchmark
Date: Wed, 14 Jun 2006 20:36:10 +0200 [thread overview]
Message-ID: <4490571A.5070102@trash.net> (raw)
In-Reply-To: <44903BA5.4030405@netfilter.org>
Pablo Neira Ayuso wrote:
> Patrick McHardy wrote:
>
>>> http://people.netfilter.org/pablo/ctnetlink/events.eps
>>
>>
>> Does "events" mean events/s?
>
>
> No, sorry, it seems that the graph is definitely misleading :(. Have a
> look at http://people.netfilter.org/pablo/ctnetlink/107520.txt
I can't seem to find the number of drops in that table, which I thought
this test was all about :) I did some plotting with the numbers myself,
comparing (1):(2)/(1) with (1):(3)/(1) (actually / 6.353 to scale the
initial UPDATE value down to NEW) shows that UPDATE events scale much
more linear than NEW events, which could either mean they get dropped
more for some reason or that the connections had a higher number of
packets in the runs with more connections (possibly because of more
retransmissions). I think we need the number of packets per connection
to make sense out of the data.
prev parent reply other threads:[~2006-06-14 18:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-13 14:59 [RFC] ctnetlink events drop benchmark Pablo Neira Ayuso
2006-06-14 7:44 ` Jozsef Kadlecsik
2006-06-14 8:04 ` Jozsef Kadlecsik
2006-06-14 12:24 ` Pablo Neira Ayuso
2006-06-14 11:38 ` Pablo Neira Ayuso
2006-06-14 13:55 ` Patrick McHardy
2006-06-14 16:39 ` Pablo Neira Ayuso
2006-06-14 18:36 ` Patrick McHardy [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=4490571A.5070102@trash.net \
--to=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=pablo@netfilter.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.