Hi guys,
We are using mapcache for seeding and serving 45 time dimensional wmts services in which each has many timeslices. We would need to understand the behavior of mapcache in regards to database connection creation upon clients' request to the wmts layers. We see many idle connections created for each wmts layer and cannot figure it how mapcache behaves in terms of querying the database for the available times and serving the tiles. Can someone shed some light for us? We would need to know the worst case scenario in terms of database connection as there is a hard limit of the maximum number of connections to our postgres cluster. I appreciate your help.
SELECT to_char(d1 at time zone 'UTC','YYYY-MM-DD"T"HH24:MI"Z"') FROM times.{table_name}
WHERE d1 >= to_timestamp($1)
AND d1 <= to_timestamp($2)
ORDER BY d1 DESC
Hi guys,
We are using mapcache for seeding and serving 45 time dimensional wmts services in which each has many timeslices. We would need to understand the behavior of mapcache in regards to database connection creation upon clients' request to the wmts layers. We see many idle connections created for each wmts layer and cannot figure it how mapcache behaves in terms of querying the database for the available times and serving the tiles. Can someone shed some light for us? We would need to know the worst case scenario in terms of database connection as there is a hard limit of the maximum number of connections to our postgres cluster. I appreciate your help.