[
https://issues.apache.org/jira/browse/JCR-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150485#comment-13150485
]
Jukka Zitting commented on JCR-3147:
------------------------------------
> parallelize a number of tasks given the number of available cores
That's also what the repository thread pool does. In addition it supports
scheduling of tasks for execution in the future it can (and should) also be
used for immediate execution of parallel tasks.
Having just a single thread pool for the repository simplifies things (even
after the added concern of keeping some threads available for high-priority
tasks), which is why IMHO we should do this.
> AbstractIndex should use the repository executor for indexing tasks
> -------------------------------------------------------------------
>
> Key: JCR-3147
> URL: https://issues.apache.org/jira/browse/JCR-3147
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core
> Reporter: Alex Parvulescu
> Priority: Minor
> Attachments: JCR-3147.patch
>
>
> The AbstractIndex still uses its own executor for indexing tasks, it should
> switch to the global repository executor.
> It should also mark the tasks as 'low priotiry' as soon as JCR-3146 gets into
> the trunk.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
