Memory Usage During Trace Expansion

[DavePearce]

There appears to be an issue where trace expansion can lead to very high memory usage on very large traces. This is likely to be partly caused by concurrency generating high memory pressure. Therefore, batching go-routines could reduce this pressure.

[achintya-7]

Hey @DavePearce
I would like to work on this issue.
Adding a worker-queue here for limiting number of go-routines should help with memory.

[DavePearce]

Well, at this stage, its not a particularly big problem for us. I have used batch processing for the various parts which have helped.

[achintya-7]

Well, at this stage, its not a particularly big problem for us. I have used batch processing for the various parts which have helped.

Ah cool.
Well I did implement a generic worker queue and incorporated it with this function. If you want, I can raise a PR.