Benchmarks OOM

Running FlowControlledMessagePerSecond benchmark with 4 forks creates out of memory exceptions.

Start by locating the FlowControlledMessagePerSecond benchmark and run it with four forks to reproduce the out-of-memory exception. Trace the memory use across the forked benchmark execution and document or correct the behavior so the benchmark completes without out-of-memory failures.

Scritto dal modello di indicizzazione a partire dal testo della issue.