Post test job artifact gzip/pigz takes a very long time on some arch's

aqa-tests end of job “gzip & pigz” compression, currently they are both done and both use -9, the highest and slowest compression, this quite frequently takes 30mins+ on some archictures (eg. windows, pLinux). I've seen pLinux take over 1 hour before!

Has it been considered going for a half-way-house, say “-5" ?

Start by locating the aqa-tests end-of-job “gzip & pigz” compression entry point and confirm where both commands use compression level -9. Compare the effect of a lower level such as -5 on the affected architectures, with completion defined by an agreed compression setting and reduced job duration.

Written by the indexing model from the issue text.