Use all available cores in the router program
Seed RNG when running tests
Increase the number of kept-alive connections backends

In acting as a reverse proxy, it's probably sensible to keep a few more than the
default (2) idle connections about. This number (20) has *not* been arrived at
empirically, and we should certainly do more testing to establish what the
correct value is for our real workload.
Run more servers as part of the test server

And increase the body size of the content they send (now randomly chosen between
8KiB and 72KiB).
Make randomly generated bodies optional in the test server
Add data and tools for benchmarking the router