<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Job Prioritization for Asynchronous Processing at Scale in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/job-prioritization-for-asynchronous-processing-at-scale/m-p/222670#M175800</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;During load test I have observed that the job executor and its thread pool is getting&amp;nbsp; overloaded and taking time to process the existing jobs and reduce the queue size to a manageable portion again. Now In a large set of pending jobs, some jobs may be more important than others. And we want to have some kind of priority based mechanism&amp;nbsp; ACTIVITI we would be able to assign some priority during process instance creation and then job executor would execute the job based on the priority. Are you planning to implement something similar in near future?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I saw something similar in CAMUNDA.&lt;/SPAN&gt;&lt;BR /&gt;&lt;A href="https://blog.camunda.org/post/2015/08/job-prioritization-asynchronous-processing/" rel="nofollow noopener noreferrer"&gt;https://blog.camunda.org/post/2015/08/job-prioritization-asynchronous-processing/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;FYI: I am using ACTIVITI 5.19.0.1 and DefaultJobExecutor.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 04 Mar 2016 07:44:17 GMT</pubDate>
    <dc:creator>kaushikmondal</dc:creator>
    <dc:date>2016-03-04T07:44:17Z</dc:date>
    <item>
      <title>Job Prioritization for Asynchronous Processing at Scale</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/job-prioritization-for-asynchronous-processing-at-scale/m-p/222670#M175800</link>
      <description>Hi,During load test I have observed that the job executor and its thread pool is getting&amp;nbsp; overloaded and taking time to process the existing jobs and reduce the queue size to a manageable portion again. Now In a large set of pending jobs, some jobs may be more important than others. And we want to h</description>
      <pubDate>Fri, 04 Mar 2016 07:44:17 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/job-prioritization-for-asynchronous-processing-at-scale/m-p/222670#M175800</guid>
      <dc:creator>kaushikmondal</dc:creator>
      <dc:date>2016-03-04T07:44:17Z</dc:date>
    </item>
    <item>
      <title>Re: Job Prioritization for Asynchronous Processing at Scale</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/job-prioritization-for-asynchronous-processing-at-scale/m-p/222671#M175801</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Which job executor are you talking about? Did you give the Async Executor a try, as it's way more performant and tweakable compared to the old job executor?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;We don't have a priority based mechanism in the engine right now.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Mar 2016 10:01:46 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/job-prioritization-for-asynchronous-processing-at-scale/m-p/222671#M175801</guid>
      <dc:creator>jbarrez</dc:creator>
      <dc:date>2016-03-07T10:01:46Z</dc:date>
    </item>
  </channel>
</rss>

