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.0 / 6.0.1 - cpu load (idle) rising compared to 5.0.4
Date: Thu, 10 Dec 2020 14:39:43 +0100	[thread overview]
Message-ID: <542D115B-5471-4561-B687-CAEAF21ED900@ipfire.org> (raw)
In-Reply-To: <16ab4738-cb8c-b61e-3c3c-cae8ab52757d@ipfire.org>

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

Hey Matthias,

I checked but I cannot confirm this on my machine.

I also asked the others on the telephone conference and nobody saw anything suspicious either.

What hardware are you using, and what rules are you using?

Best,
-Michael

> On 6 Dec 2020, at 11:08, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
> 
> Hi,
> 
> I'd like to have a little problem... ;-)
> 
> The other day I saw 'suricata 6.0.0' had its coming out - yesterday it
> was '6.0.1'. At that time I thought it might be a good idea to test the
> current version.
> 
> So I built and tested these two one after another under Core 152/64bit.
> I tested 6.0.0 some days ago, 6.0.1 yesterday. 'libhtp' was updated and
> installed too, yesterday to 0.5.36.
> 
> Both built without problems, both installed without problems, both
> showed a strange behavior while running.
> 
> Under *each* 6.0.X-version, the cpu load for '/usr/bin/suricata -c
> /etc/suricata/suricata.yaml -D -y 0:1' increased in *idle* mode from
> ~0.5%-2.0% to ~12% compared to 'suricata 5.0.4'.
> And I mean it. Idle. Nothing was going on.
> 
> Hardware:
> https://fireinfo.ipfire.org/profile/5f68a6360ffbecb6877dcac75f5b8c8030f43ce8
> 
> Can anyone confirm - or did I miss something?
> 
> Best,
> Matthias


  reply	other threads:[~2020-12-10 13:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-06 10:08 Matthias Fischer
2020-12-10 13:39 ` Michael Tremer [this message]
2020-12-10 17:46   ` Matthias Fischer
     [not found] <276ec94c-01ff-9bce-16ce-234a2336c4c7@ipfire.org>
2020-12-10 19:36 ` Michael Tremer
2020-12-11 16:03   ` Matthias Fischer
     [not found] <H000007e004e35e1.1607700049.mail.at4b.com@MHS>
2020-12-11 16:00 ` Matthias Fischer
2020-12-11 19:07   ` Matthias Fischer
2020-12-11 23:33     ` Matthias Fischer
2020-12-12  1:18       ` Kienker, Fred
2020-12-14 14:26         ` Michael Tremer
2020-12-14 15:58           ` Peter Müller
2020-12-14 18:22             ` Adolf Belka
2020-12-14 20:34             ` Peter Müller
2020-12-14 16:07           ` Kienker, Fred
2020-12-12  0:52   ` Kienker, Fred

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=542D115B-5471-4561-B687-CAEAF21ED900@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