Actions
Bug #16540
closed
Bug #16382: Improve performance of policy generation writer
We still have one lonely Future which use yet another threadpool
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
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 
Updated by 
Updated by
Actions