Results file archive is unmanageable for large builds

One user ran a job with 300k atoms. He said the results archive took an hour to decompress and then took two hours to remove all the small files.

We should come up with a better approach for this to make it more usable, or come up with clear documentation on how to best work with large builds (e.g., using API calls instead of downloading the archive.)