Details
-
Improvement
-
Resolution: Fixed
-
Major
-
11.10.5
-
Unit
-
Unknown
-
N/A
-
N/A
-
Description
The Async rendering framework allows to create jobs with a unique ID and to answer later the result of the job. So right now, async rendering is based on the Job executor to execute the threads, and our default implementation of Job executor is to use a pool with the maximum size possible (Integer.MAX_VALUE in DefaultJobExecutor for the construction of the pool).
It would be very useful to have a more fine-grained capability to be able to set the maximum number of threads for each kind of Async renderer. For example, we don't want to have a large number of threads for computing the count notifications.
Attachments
Issue Links
- blocks
-
XWIKI-17400 Specify the size of the pool for the async notification renderer
- Closed
- is related to
-
XWIKI-17334 The notification gathering thread pool configuration is not used anymore
- Closed
-
XCOMMONS-1959 Allow to define the pool size of a GroupedJob
- Closed