Re: [phpOpenTracker-User] Speeding up OpenTracker Reporting

Christopher Hogan wrote:
> 
> My only difficulty is now that I've been using it for a couple months
> the reporting engine is running very slowly. 

Same here :) I've hit about 600,000 in pot_access rows and the
simple_report takes over 20 minutes to report back.

> I've noted that by dropping the table indexes speed increases are
> possible:
> 
> " you might want to trade the speed of the phpOpenTracker API for an
> increased performance of the phpOpenTracker Logging Engine by dropping
> the table's indexes."

Uh, I think what is meant here is that logging will be faster. But if
you drop the indexes reporting will be *incredibly* slower.


> I've looked into MERGE tables however I'm a bit unsure of how to set
> something like this up for opentracker; is it possible that someone
> could provide me with an example?  Would this increase the speed of
> reporting or just logging?

Can't help there as I use postgresql and not MySQL.

> Are there any other simple, effective methods of increasing the
> reporting speed of OpenTracker?

If you find any please let us *all* know. I have tried a few things but
nothing seems to have much of an effect.

One thing I can recommend that helps a little is to use the Cache_query
PEAR module.

What are the specs for your database machine? I have a dedicated DB
server but it is only a PIII 1.6 with 512 MB RAM. I would have thought
this to be plenty but it seems not to be ... I'm thinking of getting a
faster disk and more RAM hoping that will help.

If you are really good with SQL you could turn debugging level to 2 and
see if phpOpenTracker is firing off any useless or inefficient queries.

Jean-Christian Imbeault



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf