Batch

How can we improve Azure Batch? Do you have an idea, suggestion or feedback based on your experience? We would love to hear it!

  1. Make it possible to set memory usage limitation for a batch task

    it would be nice if we can set the maximum memory usage for a specific task.
    This could help us protecting concurrent tasks from failing when one task is consuming a lot of memory.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  2. Improved error / fail sooner when pool removal is gated with a delete lock

    We recently had a case where a pool removal was 'stuck' and it appeared that the completion of the command was gated by the timeout value (which we inadvertently made very long).

    It turned out that the removal of the pool needed to delete a configuration on a subnet which was part of a VNet/RG that had a deletelock applied.

    It seems unreasonable to hang a process for a configuration change and would propose that in this case the resize should've failed once it determined it was blocked due to a delete lock on a 'sub resource'. Even better if…

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Add larger VMs

    Add support for high priority VMs in the M series. We require over 1TB of ram for a regular task at times, you currently have no VM (that cam't be preempted) that had this capability.

    Please add one, RAM requirements are only going up as the data grows and our problem is not embarrassingly parallel, so adding more machines adds both a time and financial cost (inter-node communication) that we do not want to incur.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Add features to the Azure BAtch mobile app

    The mobile app is currently not very helpful. Without the ability to remove jobs/tasks/pools, it's just a way to look at things without being able to impact any change.

    Please add the ability to look at multiple subscriptions at one, and the ability to manage Azure Batch resources.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Azure batch service should display details of previous run of task instead of overwriting while re-queuing

    Azure batch service should display details of previous run of task instead of overwriting while re queuing from low priority pool instances.
    This will help to calculate overall task/application usage. Or there should be some way to calculate overall Job/task usage including VM + storage +network etc. per job/task.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Let's use Open Source as the runtime used in Node of Azure Batch.

    Although Azure Batch is excellent, it is difficult to understand the detailed operation of Rumtime.
    Please make it OSS of Azure Batch.

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Raise the number of concurrent tasks per node core

    The idea I have in mind is to use Azure Batch to export a >100 TB Azure Table, at a much faster rate than Azure Data Factory can manage.

    Azure Tables is quoted to cope with 10,000s of simultaneous requests. To maximize my dev velocity, I would create millions of lightweight tasks and let Azure Batch runtime handle all the scheduling details.

    But there is a limit of 4 concurrent tasks per core so this would make for extremely underutilized nodes and long runtime.

    https://docs.microsoft.com/en-us/azure/batch/batch-quota-limit

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Implement tags into Batch Pools, Jobs and Tasks

    It would be great to be able to create tags into batch resources like Pools, Jobs and Tasks, as we can do it with Batch Accounts.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Show in Pool view in Portal (and over API therefore Batch Explorer) when nodes require recovery or are recovering

    Currently when a node requires recovery or is recovering, it shows up as Idle in the portal and in Batch Explorer. It should be made clear that this node is not available for use.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Azure .NET BatchClient parameterless constructor support

    Azure Batch libraries for .NET, BatchClient does'ot implement IBatchClient and doesn't provide a parameterless constructor, so building a mocking library is very difficult without the parameterless constructor. Other classes such as BobClient() and CosmosClient() has parameterless constructor, please implement it in BatchClient too.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Better error messages if pool is unable to add nodes

    If the managed resources for a vm image are missing or the node type doesnt support a requested feature (e.g. managed disk on A series vm) then the pool keeps trying to add nodes eventually hitting resize timeout, after timeout it starts again. Its not easy to debug those situations and a better error report would be very useful.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
2 Next →
  • Don't see your idea?

Batch

Categories

Feedback and Knowledge Base