> It's compress-once, decompress on somebody else's machine, so neither of those matter. Last week, there was a drive mount that was filling up, rate was rough

> It's compress-once, decompress on somebody else's machine, so neither of those matter. Last week, there was a drive mount that was filling up, rate was roughly 30Gb/hr. The contents of that mount was used by the web application. Deletion was not an option. Something that compressed quickly was needed. And on the retrieval end, when the web app needs to do decompression, seconds matter.