Arvados

The new --threads argument limits CPU and memory use, so now instead of crashing on a large (500+ container) workflow, crunchstat-summary prints lots and lots of stack traces about "too many open files" and "response not ready".

Presumably this is because it opens all of the log files up front -- only the reading/processing part is funnelled through the worker pool. In that case, it can be fixed by deferring open() until processing starts (and fixing any FD leaks).