[
https://issues.apache.org/jira/browse/SLING-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-5255:
------------------------------------
Fix Version/s: Event 4.1.0
> Jobs: allow to configure queue.maxparallel in terms of % of number of CPU
> cores
> --------------------------------------------------------------------------------
>
> Key: SLING-5255
> URL: https://issues.apache.org/jira/browse/SLING-5255
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Reporter: Alexander Klimetschek
> Fix For: Event 4.1.0
>
> Attachments: SLING-5255.patch
>
>
> The {{queue.maxparallel}} setting (how many concurrent threads can run for a
> given job queue) currently supports a fixed number of threads or -1 which
> means "as many CPU cores present on the machine". The latter is in our case
> used as a crucial default, but it's too aggressive, since it might take over
> all CPU processing.
> Since every machine has different numbers of CPUs and cores, it would be
> useful to express this config as % of number of CPU cores. This allows for
> example for a default setting of 50% that should work well on different
> machines without having to manually configure it on each instance.
> This could either be a separate setting or (better) maybe allow floating
> point numbers between 0.0 and 1.0 to express the percentage for the existing
> {{queue.maxparallel}}. E.g. 0.5 means 50% of the cores. If it's an integer,
> continue to use it as an exact number of threads to use.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
