Closed
Bug 945981
Opened 11 years ago
Closed 11 years ago
s/m1.medium/m3.medium/
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: taras.mozilla, Assigned: rail)
References
Details
it's 2.5x faster cpu-wise. However it features an ssd, which is infinitely faster. Seems well worth the 25% price increase. It'll also let us run same HVM amis as bug 944113 needs.
Reporter | ||
Comment 1•11 years ago
|
||
The new m3 medium seems nice. that 4gb ssd should be sufficient for tests
Summary: s/m1.medium/c3.large/ → s/m1.medium/m3.medium/
Assignee | ||
Comment 3•11 years ago
|
||
Using m3.medium for linux64 test slaves looks promising. 4G of SSD is quite enough for tests. linux32 isn't suported by m3 though.
Reporter | ||
Comment 4•11 years ago
|
||
(In reply to Rail Aliiev [:rail] from comment #3)
> Using m3.medium for linux64 test slaves looks promising. 4G of SSD is quite
> enough for tests. linux32 isn't suported by m3 though.
32bit userland should work fine with 64bit kernels..eg our chroot/mock thing will be fine.
Assignee | ||
Comment 5•11 years ago
|
||
We don't use mock on the test slaves. I think we can try to generate an AMI with arch set to 64 bit and 32-bit kernel and userland.
Comment 6•11 years ago
|
||
Related (but not wanting to bloat scope): Could we use mock on the test slaves? Having reproducible test environments is a good thing!
Assignee | ||
Comment 7•11 years ago
|
||
I'd rather use something more modern like lxc or docker.
Reporter | ||
Comment 8•11 years ago
|
||
(In reply to Rail Aliiev [:rail] from comment #7)
> I'd rather use something more modern like lxc or docker.
you have to use a 64bit kernel. 32bit userland will work fine
Assignee | ||
Comment 9•11 years ago
|
||
FTR, we switched to m3.medium for tst-linux64-ec2 slaves on Tue, Jan 28. Spot instances and tst-linux32 slaves are still m1.medium.
Reporter | ||
Comment 10•11 years ago
|
||
(In reply to Rail Aliiev [:rail] from comment #9)
> FTR, we switched to m3.medium for tst-linux64-ec2 slaves on Tue, Jan 28.
> Spot instances and tst-linux32 slaves are still m1.medium.
Shouldn't these bugs become resolved once we switch?
Assignee | ||
Comment 11•11 years ago
|
||
ATM we use m3.medium for all tst-linux64 instances. tst-linux32 still use m1.medium, but since we have less load on those (we don't run b2g tests on them) I would like to defer the switch over in favor of other tasks.
Updated•11 years ago
|
QA Contact: john+bugzilla
Assignee | ||
Comment 12•11 years ago
|
||
m3.medium didn't stick because we started seeing a lot of timeouts. See bug 969590 and the deps for the details.
You need to log in
before you can comment on or make changes to this bug.
Description
•