Actions
Bug #15786
closed
When computing system variables for each node, we compute the full "nodes<->policy server" mapping
Status:
Released
Priority:
N/A
Assignee:
Category:
Performance and scalability
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
Checked
Regression:
Description
this is used only for policy server, so we could compute it only for policy server
it represents a significant cost of the get node context (about 1/3 reporting in tracing, but impact of tracing may slow it down)
Updated by Nicolas CHARLES about 5 years ago
- Project changed from 41 to Rudder
- Category set to Performance and scalability
- Target version set to 5.0.14
note that this cost is roughly quadratic
Updated by Nicolas CHARLES about 5 years ago
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
Updated by Nicolas CHARLES about 5 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/2478
Updated by Nicolas CHARLES about 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|e44a4da34e21fb50722cca841f3555bcb1e8529b.
Updated by François ARMAND about 5 years ago
- Fix check changed from To do to Checked
Updated by Alexis Mousset about 5 years ago
- Subject changed from When computing system variables, we compute for each nodes the mapping all nodes<->each policy server to When computing system variables for each node, we compute the full "nodes<->policy server" mapping
- Name check changed from To do to Reviewed
Updated by Vincent MEMBRÉ about 5 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.14 which was released today.
Actions