artemp/mapnik — Issue #855: pool.hpp doesn't respect upper limit
Author: artemp
Created: 2011-10-11 16:39:02+00:00
State: open
Labels: PostGIS_Input_Driver

We're seeing that we do not max out the CPU on the postgres machine for the foss4g benchmark. The machine stays 30% idle, which seems odd.

Perhaps the connection pool is not working right?

The number of objects in a Postgres connection pool can go beyond `max_size`. https://github.com/mapnik/mapnik2/blob/master/include/mapnik/pool.hpp#L122 seems like a odd way of checking whether the desired amount of objects has already been created; when that code is run, `unusedPool_` should be 0, so when the pool is empty, mapnik creates new objects automatically.