public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@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: Sat, 12 Dec 2020 00:33:53 +0100	[thread overview]
Message-ID: <770a7f98-f35a-4a56-7fde-79e0bc86dc3d@ipfire.org> (raw)
In-Reply-To: <e6e5d522-fd59-eec9-b3cf-06eddc8db326@ipfire.org>

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

Hi,

looks as if there is something going on in the suricata forum regarding
cpu load:

=> https://forum.suricata.io/t/cpu-usage-of-version-6-0-0/706

I can't really interpret the numrous screenshots and ongoing
discussions, but could it be that this is related to what I'm
experiencing when upgrading from 5.0.x to 6.0.x?

Best,
Matthias

  reply	other threads:[~2020-12-11 23:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
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
     [not found] <276ec94c-01ff-9bce-16ce-234a2336c4c7@ipfire.org>
2020-12-10 19:36 ` Michael Tremer
2020-12-11 16:03   ` Matthias Fischer
2020-12-06 10:08 Matthias Fischer
2020-12-10 13:39 ` Michael Tremer
2020-12-10 17:46   ` Matthias Fischer

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=770a7f98-f35a-4a56-7fde-79e0bc86dc3d@ipfire.org \
    --to=matthias.fischer@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