Re: Limiting connection to mysql using old mysql module (not mysqli)
| From: | Per Jessen | Date: | Mon, 24 Sep 2007 06:37:44 +0000 |
| Subject: | Re: Limiting connection to mysql using old mysql module (not mysqli) | ||
| References: | 1 2 3 4 5 6 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-262405@lists.php.net to get a copy of this message | ||
Chris wrote:
[snip]
> will not hit the first cache because the fields are different.
> http://dev.mysql.com/doc/refman/4.1/en/query-cache-how.html
All very true, but when a busy website with 100 hits/interval has 25
duplicate queries, that 24% saved per interval. My only point was -
when you're thinking of caching, start with what is readily available
instead of re-inventing the wheel elsewhere.
>> 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.
/Per Jessen, Zürich