Closed Bug 1013554 Opened 10 years ago Closed 10 years ago

Test impact of bundles on git server load

Categories

(Developer Services :: General, task)

Product:
Developer Services
Component:
General
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: hwine, Assigned: bkero)

References

Details

In bug 985864, one of the crisis measures was to add bundles for certain key repos. That change landed at the same time as the added RAM and scheduling adjustments.

To fully support bundles on an ongoing basis, we need significant work & disk on the backend. Before undertaking, we need to determine if the effort is justified.

This bug will track the controlled removal of the existing bundles, and observed impact on both the git server and the build farm operations.
Instructions to move the bundles out of the way:

$ ssh root@git.mozilla.org
# pushd /var/lib/gitolite3/repositories/external/aosp/platform/external/icu4c.git/
# mv clone.bundle clone.bundle.disabled
# popd
# pushd /var/lib/gitolite3/repositories/external/caf/kernel/msm.git/
# mv clone.bundle clone.bundle.disabled
# popd
# exit
Change went live at 0830 PT per plan.
No impacts or issues reported as of yet. Graphite load graph has been quite flat.

Catlee: any issues on your end, or reason to continue test? If not, we can declare "test over, bundles do not improve our use cases".
Flags: needinfo?(catlee)
Declaring end of test -- no load issues observed with bundles disabled.

Yay! No value to adding infrastructure to support bundles.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(catlee)
Resolution: --- → FIXED
Component: WebOps: Source Control → General
Product: Infrastructure & Operations → Developer Services
You need to log in before you can comment on or make changes to this bug.