All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Sutter <phil@nwl.cc>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: iptables user space performance benchmarks published
Date: Fri, 19 Jun 2020 16:11:57 +0200	[thread overview]
Message-ID: <20200619141157.GU23632@orbyte.nwl.cc> (raw)

Hi Pablo,

I remember you once asked for the benchmark scripts I used to compare
performance of iptables-nft with -legacy in terms of command overhead
and caching, as detailed in a blog[1] I wrote about it. I meanwhile
managed to polish the scripts a bit and push them into a public repo,
accessible here[2]. I'm not sure whether they are useful for regular
runs (or even CI) as a single run takes a few hours and parallel use
likely kills result precision.

Cheers, Phil

[1] https://developers.redhat.com/blog/2020/04/27/optimizing-iptables-nft-large-ruleset-performance-in-user-space/
[2] http://nwl.cc/cgi-bin/git/gitweb.cgi?p=ipt-sbs-bench.git;a=summary

             reply	other threads:[~2020-06-19 14:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-19 14:11 Phil Sutter [this message]
2020-06-22 12:42 ` iptables user space performance benchmarks published Pablo Neira Ayuso
2020-06-22 13:34   ` Reindl Harald
2020-06-22 14:04     ` Phil Sutter
2020-06-22 14:11       ` Reindl Harald
2020-06-22 14:54         ` Phil Sutter
2020-06-22 15:19           ` Reindl Harald
2020-06-22 15:44             ` Phil Sutter
2020-06-22 16:29               ` Reindl Harald
2020-06-22 16:45                 ` Phil Sutter
2020-06-22 16:59                   ` Reindl Harald
2020-06-22 16:23     ` Stefano Brivio
2020-06-22 16:38       ` Reindl Harald
2020-06-22 13:40   ` Phil Sutter
2020-06-22 14:04 ` Jan Engelhardt
2020-06-22 14:35   ` Phil Sutter

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=20200619141157.GU23632@orbyte.nwl.cc \
    --to=phil@nwl.cc \
    --cc=netfilter-devel@vger.kernel.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.