Tobias Zimmergren

My feedback

  1. 38 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Azure Container Instances  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Tobias Zimmergren commented  · 

    When using AKS, one of the key benefits is the dynamic allocation of a Managed Disk (premium or standard depending on the underlying VM size).

    We're moving away from AKS for some workloads and more into the direction of ACI, but it would definitely help adoption of Container Instances if Managed Disks were an option here too - both Standard tier disks and Premium SSD.

    For burst workloads that require a quick disk and a lot of data processing, I could use Premium SSD managed disks with AKS and it worked pretty well.

    Tobias Zimmergren supported this idea  · 
  2. 31 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    11 comments  ·  Azure Container Instances  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Tobias Zimmergren commented  · 

    I'm moving away from AKS in favor for ACI in some of my scenarios. This works very well most of the time, but sometimes I have the need of burst computing and intense memory workload, something I can easily achieve with AKS because I can decide the underlying node size and pick something with 16 or more cores and a lot of memory.

    I think it would definitely increase adoption of Container Instances if it could handle bigger workloads. For my tasks running on AKS, I hit the best performance around 8 cores and 32 GB, but with ACI I have to spin up multiple ACI groups and then split the tasks across to get any sense of performance.

    Tobias Zimmergren supported this idea  · 
  3. 120 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  3 comments  ·  Azure Container Instances  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Tobias Zimmergren commented  · 

    This is a scenario that keeps coming up more and more. I'm also looking for this capability, and currently have to deploy -another- set of resources (Functions, another ACI, Web Job,...) to check if the jobs/tasks the ACI are working on are done, and if so I delete the ACI. It still means I have a Function/WebJob/some-type-of-orchestrator logic in place to ensure the cleanup.

    I've heard this several times echoed in the community as well, and it would indeed be helpful to have a new restart policy for this.

    Tobias Zimmergren supported this idea  · 
  4. 37 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Azure Resource Manager  ·  Flag idea as inappropriate…  ·  Admin →
    Tobias Zimmergren supported this idea  · 

Feedback and Knowledge Base