Bug #16540
closed
Bug #16382: Improve performance of policy generation writer
We still have one lonely Future which use yet another threadpool
Description
We have one Future in `ReportsExecutionService`. That triggers the init of `scala` thread pool. We need to get ride of it.
One warning, though: with the future, we weren't correctly handling the accumulation of them, and we should do it to avoid pilling up thread. A one-element queue can do it perfectly.
Updated by François ARMAND almost 5 years ago
- Status changed from New to In progress
Updated by François ARMAND almost 5 years ago
Actually, it's a bit more complexe, since we want to only invalidate cache for updated node. It can't be a one element queue + discard.
We will have an "offer" logic that will take the current "all" element of the one queue element, and repost the merged set.
Updated by François ARMAND almost 5 years 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/2715
Updated by François ARMAND almost 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|e490dcf0e258c1e5d162cdf5cf86978f75d96f21.
Updated by François ARMAND almost 5 years ago
- Fix check changed from To do to Checked
Updated by Alexis Mousset over 4 years ago
- Name check changed from To do to Reviewed
Updated by Vincent MEMBRÉ over 4 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.0.3 which was released today.