[
https://issues.apache.org/jira/browse/SLING-4048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-4048.
-------------------------------------
Resolution: Fixed
The jobs are not kept in memory anymore - at least not all of them. Each queue
has a cache that keeps the "next" jobs in memory. Once the cache is empty it
scans for the next set of jobs
> Avoid keeping jobs in memory
> ----------------------------
>
> Key: SLING-4048
> URL: https://issues.apache.org/jira/browse/SLING-4048
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Event 3.4.0
>
>
> Currently all jobs for a single instance are hold in memory and put into the
> queues. This is not optiomal, especially for a large amount of jobs. In
> addition it makes configuration changes, queue updates etc. more complicated.
> We should revert this and let a queue only pick a job from the resource tree
> when it has a free processing space.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
