Re: Joomla MySQL query performance affected by anything non-server related?
| From: | TG | Date: | Wed, 05 Nov 2008 22:14:23 +0000 |
| Subject: | Re: Joomla MySQL query performance affected by anything non-server related? | ||
| Groups: | php.db | ||
| Request: | Send a blank email to php-db+get-45600@lists.php.net to get a copy of this message | ||
Thanks for the response, Chris. I have analyzed, optimized, checked, etc.
Everything looks relatively good/healthy on the server side of things. It
is MyISAM. That's one thing I don't really know very well, the benefits of
the different DB engines.
Not sure if I'm going to be able to see a process list when there are
problems because the problems are really intermittant.
When I do "show processlist" logged in as the same user, I don't see anything
else executing.
The client gets an average of 600 hits per day on their site. Nothing too
crazy. That's the other thing that's driving me nuts. They get traffic,
but it shouldn't be so much that it's causing issues ilke this.
Shouldn't have to make such radical changes for this site. All I can think
is that it's an issue with their server and/or other customers on the same
shared server.
-TG
----- Original Message -----
From: Chris <dmagick@gmail.com>
To: TG <tg-php@gryffyndevelopment.com>
Cc: php-db@lists.php.net
Date: Thu, 06 Nov 2008 08:45:16 +1100
Subject: Re: [PHP-DB] Joomla MySQL query performance affected by anything
non-server related?
>
> > UPDATE jos_content SET hits = ( hits + 1 ) WHERE id='123'
> >
> > The log says this took 7 seconds. There's an index on "id". There are
only
> > 400 or so records in the whole table. It's not like there are a million
> > records and no index.
> >
> > Is there ANY rational reason this query would EVER take 7 seconds to
execute?
>
> It could be worth either doing an analyze
> (http://dev.mysql.com/doc/refman/5.0/en/analyze-table.html) or possibly
> doing a dump/restore - in case there is lots of "bloat" either in the
> indexes or tables. Normally you wouldn't see this with mysql (especially
> myisam) but it's worth a shot.
>
> What other queries are running at the same time? (use 'show processlist'
> inside mysql to get a list), maybe you're getting lots of hits to the
> same tables and myisam is locking everything, and it's time to convert
> to innodb.
>
>
> --
> Postgresql & php tutorials
> http://www.designmagick.com/
>
>