Project

General

Profile

Actions

Bug #24844

open

Software updates need to be special cased for performance in nodefact

Added by François ARMAND 17 days ago. Updated 9 days ago.

Status:
Pending release
Priority:
N/A
Category:
Performance and scalability
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No

Description

In system update plugin in Rudder 8.0, we were forced to build an ad-hoc cache for software updates with dedicated LDAP queries.

Given that, it seems that it should be part of CoreNodeFact and always be in memory, or, if we prefer to let the cache live only in system update plugin, have the specialized LDAP request built for it.

It we choose to add software updates to CoreNodeFact, we need to have a better guess at memory implication (how much memory for 15000 nodes with a mean of 200 updates ?).
And we will need to update node search and system update to use it.

Actions #2

Updated by François ARMAND 9 days ago

SoftwareUpdate looks like it takes around 20kB per node for 200 updates. So we are talking about 300Mo for 15k nodes, it seems OK. We will try to add it, test in perf machine, and see how it behaves.

Actions #3

Updated by François ARMAND 9 days ago

  • Status changed from New to In progress
  • Assignee set to François ARMAND
Actions #5

Updated by François ARMAND 9 days ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/5662
Actions #6

Updated by Anonymous 9 days ago

  • Status changed from Pending technical review to Pending release
Actions

Also available in: Atom PDF