Roughly 0.5 second gap between http tasks

I’m consistently seeing a gap of ~0.5 seconds between the end of one task and the beginning of the next task that is severely slowing down my workflow. I’m running conductor using docker-compose up locally. I’m not sure what the problem is. Any guidance would be greatly appreciated.

[ghost]

Hi @fnolla-carecloud, i managed to decrease delay between sequencial tasks by changing the class com.netflix.conductor.core.execution.tasks.SystemTaskWorkerCoordinator at this line:

List<String> polledTaskIds = queueDAO.pop(taskName, realPollCount, 200);

to

List<String> polledTaskIds = queueDAO.pop(taskName, realPollCount, 0);

Before it was wating up to 200 ms before returning polledTasksIds. Now it just get the messages that are already in the queue, not waiting to pop realPollCount messages. For example if realPollCount = 10, it doesn’t matter if there are only 1 message in the queue, it returns right away.

Also this line is important:

this.pollInterval = config.getIntProperty(“workflow.system.task.worker.poll.interval”, 50);

It defines the interval between polling to the system worker task queues. The bigger this inteval the bigger the latency between sequencial tasks.

I also used async indexing of IndexDAO

[github-actions[bot]]

This issue was closed, because it has been stalled for 7 days with no activity.