The number of connections is presumably only important if we speak
about the number of concurrent connections. If each query can be
dealt with faster due to caching, the number of concurrent
connections should drop.
Err no - it still has to connect to the database (thus use a
connection slot) to even get to the cache.
Err yes - a query replied to out of cache will take less time to
complete, therefore the connection will be given up faster, therefore
less _concurrent_ connections.
I guess my idea of concurrency is different to yours.
100 people come to your website - that's still going to be 100 connections to the database, regardless of where the results come from.
--
Postgresql & php tutorials
http://www.designmagick.com/