From: "Daniel Weismüller" <daniel.weismueller@ipfire.org>
To: development@lists.ipfire.org
Subject: APU / Suricata Benchmarks
Date: Tue, 26 Mar 2019 20:47:58 +0000 [thread overview]
Message-ID: <20190326204758.Horde.DnISwUw2OMOxDZiG-LkF5cz@whytea.ipfire-zuhause.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 340 bytes --]
Here are the first bidirectional iperf benchmarcs with the apu
797/922 mbit/s without suricata
23/68 suricata no rules active
30/60 suricata with 1 rule active
28/63 suricata with 7 rules active
top cpu usage
10%us 27%sy 0%ni 50%id 0%wa 1,5%hi 12%si 0%st
Wow, this is slower than I imagined.
Tomorrow I try better hardware.
-
Daniel
next reply other threads:[~2019-03-26 20:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 20:47 Daniel Weismüller [this message]
2019-03-27 9:57 ` Michael Tremer
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=20190326204758.Horde.DnISwUw2OMOxDZiG-LkF5cz@whytea.ipfire-zuhause.de \
--to=daniel.weismueller@ipfire.org \
--cc=development@lists.ipfire.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