The C/C++ driver's connection pool does not eagerly create connections even when the minPoolSize config is set. This is surprising behavior and has lead to difficult-to-diagnose performance issues when the first operation has wildly different performance from subsequent operations.

What's more is that the driver spec seems to require this behavior:

If minPoolSize is set, the Connection Pool MUST be populated until it has at least minPoolSize total Connections.