public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: suricata 6.0.2 - cpu load (idle) rising compared to 5.0.X
Date: Tue, 02 Mar 2021 21:28:27 +0000	[thread overview]
Message-ID: <1BDC7015-486B-4033-B10F-B047D4524952@ipfire.org> (raw)
In-Reply-To: <fdfc93ea-9994-b13c-ad51-0b12ebc54854@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 974 bytes --]

Hello,

> On 2 Mar 2021, at 19:55, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
> 
> Hi,
> 
> for the records:
> 
> Today I tested 'suricata 6.0.2' and '5.0.6' on Core 153/x86_64.
> 
> 'suricata' was activated only on RED with a few rules from
> "EmergingThreats.net".
> 
> Hardware:
> https://fireinfo.ipfire.org/profile/5f68a6360ffbecb6877dcac75f5b8c8030f43ce8
> 
> *Nothing* has changed here, CPU load still rises from ~0.7% in idle mode
> to ~7-9% as soon as 'suricata' is started.
> 
> No further mails or reactions in the suricata forum on Michaels last
> comment (https://redmine.openinfosecfoundation.org/issues/4096#note-29).

Yes, that is very sad. I suppose we won’t get anything.

We can only hope that they are going to replace the affected code in Suricata 7. Until then, we are stuck on Suricata 5.

> Should I send an update to '5.0.6' or '6.0.2'? ;-)

Just for 5.0.6, please :)

-Michael

> Best,
> Matthias


      reply	other threads:[~2021-03-02 21:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-02 19:55 Matthias Fischer
2021-03-02 21:28 ` Michael Tremer [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=1BDC7015-486B-4033-B10F-B047D4524952@ipfire.org \
    --to=michael.tremer@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