Closed Bug 1304058 Opened 8 years ago Closed 6 years ago

investigate using a pricing safety factor other than 2x

Categories

(Taskcluster :: Services, defect)

Product:
Taskcluster
Component:
Services
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: jhford, Unassigned)

References

Details

EC2 pricing "magically" keeps the actual price paid similar to the bid amount submitted until we get spot killed.  What we do now is take the max price for a type/region/az bucket in the last half hour and use that value for price comparisons.  When we submit the real bid, we take 2x that value for safety around spot kills.

The work here is to see how changing 2.0 to something lower would affect the spot kills.

For this project we'd need to have solid per-region/type/az spot kill metrics, as well as submissions, etc.
Summary: investigate using a safety factor other than 2x → investigate using a pricing safety factor other than 2x
Spot pricing has changed completely, we're likely to move towards a model of reliability based provisioning choices.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Component: AWS-Provisioner → Services
You need to log in before you can comment on or make changes to this bug.