Closed Bug 1022838 Opened 8 years ago Closed 8 years ago

add r3.xlarge to our bids

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

x86_64
Linux
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: taras.mozilla, Assigned: rail)

References

Details

Attachments

(1 file)

r3.xlarge has same compute as c3.xlarge, 4x as much ram and almost no demand, so it costs less atm(0.0321 vs 0.0322 :)

Judging by spot price history the price on these doesn't fluctuate as much as other nodes.

It should get a higher perf constant than m3.xlarge due to more ram.
I'm going to take a look at this.

The plan is to test it on some on-demand instances first and then push to spot instances.

Any objections against performance constant set to 1.2? Our current values are here:

http://hg.mozilla.org/build/cloud-tools/file/dbdf3c0695e8/configs/watch_pending.cfg#l39
Assignee: nobody → rail
Attached patch r3.diffSplinter Review
bld-linux64-ec2-001 is r3.xlarge now, will check https://secure.pub.build.mozilla.org/builddata/reports/slave_health/slave.html?name=bld-linux64-ec2-001 

We can land this change tomorrow.
Attachment #8437122 - Flags: review?(catlee)
Attachment #8437122 - Flags: review?(catlee) → review+
We have ~100 r3.xlarge running in production now. \o/
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.