locked
How many Azure Virtual Machine instances can Azure Batch use ? RRS feed

  • Question

  • How many Azure Virtual Machine instances can Azure Batch use ?
    I want to know that Azure Batch can use 10,000 Azure Virtual Machine instances or not.
    VM = Azure Virtual Machine.

      "What if you have access to 16 cores, 100 cores, 10,000 cores or even 100,000 core when you needed it"
      http://azure.microsoft.com/en-us/services/batch/

    Regards
    Yoshihiro Kawabata

    Thursday, October 30, 2014 2:06 AM

Answers

  • Batch has no problem with 10,000 VMs. We spread deployments out across physical clusters in a region to give you scale. We did a test last week with 20,000 VMs.

    Running at this scale does require working with our capacity planning team, and could involve running across multiple regions. We do this regularly with customers.

    Let us know if you have a project that you would like to try at large scale.

    Alex

    Thursday, October 30, 2014 8:54 AM
  • Care should be taken when managing especially large collections of CloudTask, CloudJob, etc objects in memory. We recommend leveraging the DetailLevel feature to limit the number of properties marshaled and populated as well as paging use patterns.

    Enumerating large collections (casual use of our IEnumerable/IEnumerableAsyncExtended) is just fine at any DetailLevel.

    DetailLevel also exposes ODATA filtering to help control collection sizes.

    daryl
    Thursday, October 30, 2014 11:19 AM

All replies

  • Batch has no problem with 10,000 VMs. We spread deployments out across physical clusters in a region to give you scale. We did a test last week with 20,000 VMs.

    Running at this scale does require working with our capacity planning team, and could involve running across multiple regions. We do this regularly with customers.

    Let us know if you have a project that you would like to try at large scale.

    Alex

    Thursday, October 30, 2014 8:54 AM
  • Care should be taken when managing especially large collections of CloudTask, CloudJob, etc objects in memory. We recommend leveraging the DetailLevel feature to limit the number of properties marshaled and populated as well as paging use patterns.

    Enumerating large collections (casual use of our IEnumerable/IEnumerableAsyncExtended) is just fine at any DetailLevel.

    DetailLevel also exposes ODATA filtering to help control collection sizes.

    daryl
    Thursday, October 30, 2014 11:19 AM
  • Thank you Alex, for your quick answer.
    over 10,000 VM so exciting.

    I will start to talk our customers and our partners.

    Regards,
    Yoshihiro Kawabata

    Thursday, October 30, 2014 2:28 PM
  • Thank you, DarylMsft for nice programing information.

    I will start to learn Azure Batch more and more.

    Regards,
    Yoshihiro Kawabata

    Thursday, October 30, 2014 2:29 PM