Closed
Bug 1181373
Opened 10 years ago
Closed 10 years ago
Produce S3 bundles for more repositories
Categories
(Developer Services :: Mercurial: hg.mozilla.org, defect)
Developer Services
Mercurial: hg.mozilla.org
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: gps, Assigned: gps)
Details
Server metrics reveal there are a number of high-traffic repositories that we're not generating bundles for. This includes:
build/talos (100+ GB/day)
integration/b2g-inbound (200+ GB/day)
releases/mozilla-esr38 (200+ GB/day)
projects/ash (20+ GB/day)
projects/holly (20+ GB/day)
projects/jamun (20+ GB/day)
projects/larch (20+ GB/day)
projects/oak (20+ GB/day)
I'm going to enable S3 bundles for these repositories in hopes of reducing clone load.
Assignee | ||
Comment 1•10 years ago
|
||
This is deployed. https://hg.mozilla.org/hgcustom/version-control-tools/rev/fcbc77ee784e
I manually triggered generation of build/talos, integration/b2g-inbound, and releases/mozilla-esr38 to get them out there since they account for so much traffic and I want the logs from 2015-07-08 to reflect having access to the bundles.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•