consider doing multithreaded repacking

NEW
Unassigned

Status

Release Engineering
Release Automation
P3
normal
5 years ago
4 years ago

People

(Reporter: bhearsum, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
We currently do repacks serially on a single machine. While they're mostly I/O bound, they still might get some benefit from doing 2 or more at the same time on a single machine. We should try this out at least, even if it doesn't pan out.

If we do this we'll have to be careful when doing any build system operations that produce artifacts that aren't locale specific. We might need to use a semaphore or lock to avoid concurrency issues.
(Reporter)

Comment 1

5 years ago
A quick way to test whether this would be viable is to run two instances of the repack script in parallel on one machine.

Also, this might not be worthwhile to do in create-release-repacks.py given the currently work going on to port all repacks to mozharness.
(Assignee)

Updated

4 years ago
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.