I have the same problem. The new DS\Task solution is not as fast as DS 6.9.

So is it normal that it takes 5 minutes and more? If i run the tasks one by one they run faster than when they are steps of a job.

Just an update: I got some info that when tasks are being put into a series as a job they have trouble understanding when the previous task completed in order to start the following task.

There's some truth to what you just said.  Consider two scenarios:

1) Build 3 tasks, fire each of them off one after another with the option marked to not allow other tasks to run simultaneously.  The agent receives all 3 nearly at the same time but queue's them up until one is finished.  The agent will know immediately when one finishes and thus be able to fire the next one off in quick succession.

2) Build 3 tasks in a job and fire off the job.  Task 1 is sent to the agent which has to report to the task server that the task is complete.  Task server has to send data up (dataloader) to the NS to report task is complete (we're not sure how fast this happens, but it appears to be nearly immediate).  NS has to process this data, and then send the next task.

What is curious to me is why this takes 5 minutes.  My first thought was "ah - 5 minutes is the delta update schedule!" but I'm having a hard time believing that.  Second thought was "Ah, 5 minutes is the fail-over check-in interval out of the box!"  That has more merit (later).  The third thought though is that I'm confident that most of our DS users are seeing consequtive tasks run a lot faster than this.  In fact, in one scenario. we've had to introduce a delay tactic to prevent a task from coming down to the client during reboot tasks.

Based on all of this, I'm leaning toward an actual problem.  Is it possible you have communication issues with either the task server or the NS?  Performance issues in the console?  Other errors in the logs?  Are the ports for Task binding correctly? (NS ports are 50120-50124 but site servers should be missing 2,3)  If you don't have a port binding correctly, or CTDataloader isn't reporting up correctly, that would cause the 5 min delay you're seeing (fail-over manual check-in for the next task).

Take a peek around at the rest of what's going on and see if maybe something's broke.  Then let us know.

I am still seeing this issue. It doesn't look like a port issue as the firewall is off.

Hello again,

since after tweaking around a little we also continue having this issue, I am reverting:

- We don't seem to have communication issues with the task server or with the NS.

- Our console always seems a bit lame to me and the waiting after we click on something irritates me, I guess this isn't normal?

- We have got rid of most errors in the logs.

- Where do we find the Port Binding?

Thanks for the help!

If you have configured a server job (vs a client job) you'll get this 5 minute delay.  Could that be related at all?