The MirrorMaestro currently has a hard-coded max size of 4 on its connection pool, which limits its ability to mirror requests at higher rates without many of the requests timing out waiting for a connection. If we intend to support rates up to 1.0, then we'll also need to allow users to configure the connection pool size accordingly. Alternatively, we could size the pool automatically based on the mirror maestro's rate.