search

dotnet / dnceng

.NET Engineering Services
MIT License
25 stars 19 forks source link

Increase customer satisfaction by increasing queue size using Azure Spot VMs and/or agentless queues #1214

Open dotnet-bot opened 2 years ago

dotnet-bot commented 2 years ago

Migrated from https://github.com/dotnet/core-eng/issues/9885

@akoeplinger wrote:

Azure recently introduced a new VM type that sounds ideal for our Helix queue usage: https://azure.microsoft.com/en-us/blog/announcing-the-general-availability-of-azure-spot-virtual-machines

These VMs are significantly cheaper and can be evicted when a capacity/price threshold is reached. We could use these to help with https://github.com/dotnet/core-eng/issues/9539.

From @MattGal:

I think the main questions that have to be answered are 1) how often do they realistically delete spot instances, and 2) what is the actual cost savings

Recently Triaged Issues

All issues in this section should be triaged by the v-team into one of their business objectives or features.

MattGal commented 2 years ago

There's a LOT of context lost in the porting from https://github.com/dotnet/core-eng/issues/9885 . Either way, we should probably discuss this one in triage since all the investigation parts are done. I removed the epic link so we can discuss this in triage this week.

dougbu commented 6 months ago

This epic and Spot VMs for Builds overlap. In addition we could put the creation side issues into Improve helix-machines Infrastructure and move the consumption side into dotnet/arcade. Feels too off in a corner at the moment.