-
Notifications
You must be signed in to change notification settings - Fork 121
CLI option --poll-until-tasks-complete is too slow on many tasks #346
Comments
You can also try the counting API: If that is insufficient, is it possible to add task deletion into your workflow to reduce the count? Otherwise, there will need to be a feature to support OData filtering on that command. |
My use case: I have about 170 jobs with each 500 tasks. Together these are 85.000 tasks (total task number). Workaround 1: Here I have first compute the total task number with the command above. Than I have to write a while loop with this command and compare output line Workaround 2: Delete tasks when they are completed: How could this be easily done? And if this could be done, the first call of Workaround 3: Do you have other ideas? |
Apologies for the delay: Workaround 1, that's correct except you should be able to programmatically parse the output with Workaround 2, correct, a filter will need to be implemented. For other workarounds, unfortunately you may need to perform a short term integration with Azure CLI and combine some features between the two. |
What about the
Could this be fast enough? Does this only output jobs specified in the jobs configuration file or does this command lists all jobs in the batch account? The documentation is not clear to me: " |
Apologies for the delay. Without a |
Problem Description
I use cli option
--poll-until-tasks-complete
too wait until all jobs completed. This option is too slow when you have many tasks (e. g. 80.000). So this option is unusable for me.Batch Shipyard Version
3.9.1
The text was updated successfully, but these errors were encountered: