Activiti

Optimize job acquisition (exclusive jobs / maxJobsPerAcquisition)

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 5.11
  • Component/s: Engine
  • Labels:
    None
  • Number of attachments :
    0

Description

The JobExecutor.maxJobsPerAcquisition property should not be extended to exclusive jobs:
A batch of exclusive jobs is assigned to a single thread, so maxJobsPerAcquisition should be interpreted as the maximum number of distinct, non-exclusive jobs.

AT

  • maxJobsPerAcquisition is interpreted as the maximum number of distinct, non-exclusive jobs.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Tom Baeyens added a comment -

Any volunteer to implement this?

Show
Tom Baeyens added a comment - Any volunteer to implement this?
Hide
Permalink
Daniel Meyer (camunda) added a comment -

I'll take care of this

Show
Daniel Meyer (camunda) added a comment - I'll take care of this
Hide
Permalink
Nico Rehwaldt (camunda) added a comment - - edited

No simple solution to satisfy

"maxJobsPerAcquisition is interpreted as the maximum number of distinct, non-exclusive jobs".

Will go with an optimization now which is to remove the lines

jobsInThisAcquisition += jobIds.size();
if(jobsInThisAcquisition >= maxJobsPerAcquisition)

{ break; }

from the JobAcquisitionCmd, only.

Show
Nico Rehwaldt (camunda) added a comment - - edited No simple solution to satisfy "maxJobsPerAcquisition is interpreted as the maximum number of distinct, non-exclusive jobs". Will go with an optimization now which is to remove the lines jobsInThisAcquisition += jobIds.size(); if(jobsInThisAcquisition >= maxJobsPerAcquisition) { break; } from the JobAcquisitionCmd, only.

People

  • Assignee:
    Nico Rehwaldt (camunda)
    Reporter:
    Daniel Meyer (camunda)
Vote (0)
Watch (3)

Dates

  • Created:
    Updated:
    Resolved: