Project

General

Profile

Actions
Copy link

Bug #16540

closed

Bug #16382: Improve performance of policy generation writer

We still have one lonely Future which use yet another threadpool

Added by François ARMAND almost 5 years ago. Updated over 4 years ago.

Status:
Released
Priority:
N/A
Assignee:
Vincent MEMBRÉ
Category:
Performance and scalability
Target version:
6.0.3
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
Checked
Regression:

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.

Actions
Copy link

Also available in: Atom PDF