Closed Bug 993307 Opened 11 years ago Closed 11 years ago

Turn down parallelism in update verify

Categories

(Release Engineering :: Release Automation, defect, P3)

Product:
Release Engineering
Component:
Release Automation
Platform:
x86
All
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: nthomas, Unassigned)

References

Details

Bug 989239 is tracking issues for IT oncall when we do an update verify for a Firefox desktop beta. I don't think the verify itself is asking for more data, although throughput to AWS may be variable. The load from tests & outside world has increased though, so base traffic + verify gets too much for the cluster. The short term fix on our side is to modify lines like releaseConfig['updateVerifyChunks'] = 6 in our release configs, say down to 4. This will mean update verify takes longer, but be nicer to the cluster. The real fix is bug 710461, which will prevent us downloading the same file multiple times. Other ideas ?
Are we okay with the current parallelism now?
Priority: -- → P3
I think so.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.