Open Bug 1608446 Opened 4 years ago Updated 2 years ago

Download and extract test packages in parallel

Categories

(Testing :: General, enhancement, P3)

Version 3
enhancement

Tracking

(Not tracked)

People

(Reporter: marco, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(3 files)

We are currently downloading and extracting them one after the other.
While parallel extraction by itself probably wouldn't buy us much, in this case we can parallelize downloads and extractions (so while we extract a package, we can start downloading the next).

Priority: -- → P3
See Also: → 1421734

I had an old patch that I dusted off to give this a shot. The results are here:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=c67d3f85b376cb68b87fb2ac06461e0a9d1604d1

It looks like most of the time is spent in extraction. zstd will help a bit there.

If we shell out to tar, we can drastically improve our extraction times. See here:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=bc1f33c8c8329d708e99470f27f0bb9bf958cdfa

(In reply to Chris AtLee [:catlee] from comment #2)

If we shell out to tar, we can drastically improve our extraction times. See here:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=bc1f33c8c8329d708e99470f27f0bb9bf958cdfa

e.g. unpacking target.common.tests.tar.gz takes 5s with tar instead of 50s with python's tarfile module.

Assignee: nobody → mozilla

When I was looking at the patches for this bug, it was a bit difficult to see
what was included in the common test package (when looking at the extract lists
in mozharness). At this point, it'd probably be reasonable to make the things
included explicit, rather than implicit via excludes.

Though Bug 1330421 makes that difficult in other ways; I was wondering it might
make sense to move the generated/compiled bits to their own package, in
preperation for Bug 1628981. (Though a bunch of that stuff could in toolchain
packages probably, instead)

The bug assignee didn't login in Bugzilla in the last 7 months.
:ahal, could you have a look please?
For more information, please visit auto_nag documentation.

Assignee: mozilla → nobody
Flags: needinfo?(ahal)
Flags: needinfo?(ahal)
See Also: → 1657606

This looks like it's still an issue, though unsure why the attached patches never landed. It's unclear if moving to fetches (like bug 1657606 and revision in here accomplishes) is enough to fix the problem completely. If so we should likely dupe this to bug 1657606.

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: