Best practice: profile before adding memcached?
howachen at gmail.com
Tue Feb 6 03:03:59 UTC 2007
On 2/6/07, Brian Moon <brianm at dealnews.com> wrote:
> > I would suggest the best practice is to run the `explain` statements
> > of your critical SQL before doing any codes' profiling.
> Not to throw yet another idea on here, but the mysql slow query log
> (assuming you are using mysql) or the equivelant in your dbms can be
> most useful. Sometimes explain and profiling does not show you where
> bottlenecks are in a high volume production environment. A query that
> takes .5 seconds does not sound that bad until there are 100 of them on
> a myisam table at one time.
at the time the developer is writing the query, they should make sure
the query is fast and efficient, if they are not sure, use the explain
of coz this does mean the application will be free of slow query in
production use, but should be a good practice.
More information about the memcached