CLI Built In Compression Improvement

[rosensteinsamuel1]

Is your feature request related to a problem? Please describe.
The built in CLI compression (ie the --archive flag) is significantly slower than compressing a file (using the native os zip function) and uploading afterwards.

For instance, for an 18GB file, the CLI compress method is ~6 minutes slower than first zipping the file and then uploading with the CLI.

The time taken for the “jf rt u –archive zip” command:

real	25m42.726s
user	27m24.740s
sys	3m5.129s`

Zipping the file separately and then using the “jf rt u” (without archiving):

real	19m32.809s
user	14m26.490s
sys	2m1.634s

Describe the solution you'd like to see
Ideally the performance of the CLI compression should be comparable to that of the natural zip command outside of the CLI. Any separate step outside of the CLI adds additional complexity for pipeline maintenance.

Describe alternatives you've considered
Using an zip command separate from the CLI to first compress the file. Afterwards, the CLI can be used to upload this file. This is the current workaround but still causes pain points for pipeline clarity and maintenance.