The document mentions that connections_per_pool defaults to unlimited, which means there is no limit to the number of connections that can be created in each connection pool.
You can use MongoPool::setSize to limit: http://php.net/manual/en/mongopool.se...
In addition, Mongo 2.2+ with Mongo PECL extension 1.3+ (beta) can support single connection reuse, it is recommended to pay attention.
UPDATE:
On top of this new framework, new functionality is also implemented to provide read preference support that comes with MongoDB 2.2. The new framework no longer has the concept of a connection pool, but instead make sure there is only one connect per node/db /username.
This means that a fixed number of connections can be maintained like an nginx proxy, like a "pipeline", but a connection pool is not equal to a pipe.
The ext-mongo solution of MongoDB 2.0 and 1.2.x does not support pipes. Concurrent scripts will not reuse connections. When a script releases the connection used, another script can use it from the connection pool. .
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
The document mentions that connections_per_pool defaults to unlimited, which means there is no limit to the number of connections that can be created in each connection pool.
You can use MongoPool::setSize to limit: http://php.net/manual/en/mongopool.se...
In addition, Mongo 2.2+ with Mongo PECL extension 1.3+ (beta) can support single connection reuse, it is recommended to pay attention.
UPDATE:
This means that a fixed number of connections can be maintained like an nginx proxy, like a "pipeline", but a connection pool is not equal to a pipe.
The ext-mongo solution of MongoDB 2.0 and 1.2.x does not support pipes. Concurrent scripts will not reuse connections. When a script releases the connection used, another script can use it from the connection pool. .