Project

General

Profile

Actions

Story #20991

open

Let container requests specify whether they'd rather run fast or run cheap

Added by Brett Smith 5 months ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
Crunch
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Story points:
-

Description

Most complete implementation would be something like:

  • There's a field somewhere on container requests that expresses whether it would be better for the container to finish ASAP (run fast) or whether it's willing to wait to reduce costs (run cheap)
  • Configuration lets the administrator set a default policy for container requests that come in without a preference
  • Configuration lets the administrator set an optional override for all container requests, putting the preference under the control of the administrator and out of the hands of individual users

This would let us make more sophisticated scheduling decisions like:

  • If preemptible instances are not available, should we switch to reserved instances (run fast) or wait until the spot price cools (run cheap)?
  • If the cheapest instance type to accommodate a container is not immediately available, should we request a bigger instance (run fast) or wait until it becomes available (run cheap)?

Related issues

Related to Arvados - Feature #18181: Ability to specify a % of compute instance price that user is willing to go over from cheapestNew

Actions
Related to Arvados - Feature #20979: Research spot instance retry strategiesNewSarah Zaranek

Actions
Actions #1

Updated by Brett Smith 5 months ago

  • Related to Feature #18181: Ability to specify a % of compute instance price that user is willing to go over from cheapest added
Actions #2

Updated by Brett Smith 5 months ago

  • Related to Feature #20979: Research spot instance retry strategies added
Actions

Also available in: Atom PDF