Project

General

Profile

Bug #15028

Improve rsyslog performance by simplifying parsing of reports

Added by Nicolas CHARLES 6 months ago. Updated 5 months ago.

Status:
Released
Priority:
N/A
Category:
Performance and scalability
Target version:
Severity:
User visibility:
Effort required:
Priority:
0

Description

We are not using serials anymore for rules, yet we check them in the regexp of rsyslog in rudder server

With super high load (950k message in 8 minutes), it causes super high CPU usage, and saturates at 200% + CPU

not parsing them makes it stays below 200% rather above 200% cpu, with moments at 160% CPU


Related issues

Related to Rudder - Bug #14506: Improve 'rsyslog' to manage larger load of reportsReleasedActions

Associated revisions

Revision dc7fdeac (diff)
Added by Nicolas CHARLES 6 months ago

Fixes #15028: Improve 'rsyslog' configuration for insanely high load

History

#1

Updated by Nicolas CHARLES 6 months ago

  • Related to Bug #14506: Improve 'rsyslog' to manage larger load of reports added
#2

Updated by Nicolas CHARLES 6 months ago

  • Description updated (diff)
#3

Updated by Nicolas CHARLES 6 months ago

  • Status changed from New to In progress
  • Assignee set to Nicolas CHARLES
#4

Updated by Nicolas CHARLES 6 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to Alexis MOUSSET
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/1450
#5

Updated by Nicolas CHARLES 6 months ago

  • Status changed from Pending technical review to Pending release
#9

Updated by Alexis MOUSSET 5 months ago

  • Subject changed from Improve 'rsyslog' configuration for insanely high load to Improve rsyslog performance by simplifying parsing of reports
#10

Updated by Vincent MEMBRÉ 5 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 5.0.12 which was released today.

Also available in: Atom PDF