Reduce scratch disks for GCP pools
Categories
(Release Engineering :: Firefox-CI Administration, task)
Tracking
(Not tracked)
People
(Reporter: ahal, Assigned: jcristau)
References
(Blocks 1 open bug)
Details
Attachments
(7 files, 1 obsolete file)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review |
We realized that most of our GCP pools have way too many scratch disks. We likely only need a single disk (or the minimum for the given instance type) per pool.
More information on valid # of SSDs by instance type here:
https://cloud.google.com/compute/docs/disks/local-ssd
Reporter | ||
Comment 1•2 years ago
|
||
Reporter | ||
Comment 2•2 years ago
|
||
Depends on D181112
Updated•2 years ago
|
Assignee | ||
Comment 3•2 years ago
|
||
The extra scratch disks make it more likely we run out of quota and can't spin up as many workers as we'd like, so they might be hurting our end-to-end times. We should double check whether they really help performance.
Assignee | ||
Comment 4•2 years ago
|
||
Stealing this.
Assignee | ||
Comment 5•2 years ago
|
||
This was copied over from the corresponding aws pool, but is not true in
GCP, since each scratch disk is 375GB.
Assignee | ||
Comment 6•2 years ago
|
||
These only run short/simple tasks, they don't need 4x375GB scratch
space, even with capacityPerInstance: 8
.
Assignee | ||
Comment 7•2 years ago
|
||
The linux-gcp workers for the ci-t, code-analysis-{1,3}, nss-{1,3},
releng-{t,1,3} and taskgraph-t groups are likely not IO bound and can do
with a single scratch disk.
Assignee | ||
Comment 8•2 years ago
|
||
Assignee | ||
Comment 9•2 years ago
|
||
Comment 10•2 years ago
|
||
Assignee | ||
Comment 11•2 years ago
|
||
Error out if we define a pool with too few scratch disks for the machine type.
Comment 12•2 years ago
|
||
Assignee | ||
Comment 13•1 year ago
|
||
Let's call this one done and we can have further improvements in separate bugs.
Updated•1 year ago
|
Description
•