Re: [phpOpenTracker-User] Speeding up OpenTracker Reporting

Christopher Hogan wrote:
> 1.2 ghz ITOX rack mount 512 ram running Free BSD with MySQL version
> 3.23.52 and delay_key_write enabled.  This is a dedicated database
> server.

I'm in the same ball park. 1.6GHz PIII with 512MB RAM running Red Hat
Linux 8.0 (custom 2.4.21 kernel) with PostgreSQL 7.3.3. Also a dedicated
database.

I tried running the full simple report last night and it took over 30
minutes for only 57,000 log entries.

Sebastian did have a point though that the simple report is just an
example and not necessarily the best (fastest) way of generating
reports. Maybe what we should look into is writing a faster report
generating tool?

I've already written my web-based front-end for phpOpenTracker so I
would be happy to contribute my efforts to writing a new reporting tool.
However I can't begin to guess as to how to write a 'fast' reporting tool.

If Sebastian and other people  could throw some ideas about as to what
is needed to make a reporting tool fast I'll happily start coding it.

Also a point was made that most people don't need access to old data.
While this may be true the current problem is not accessing to a lot of
old data, it is accessing a lot of new data.

I can understand that if someone says "It takes too long to generate a
report over the last 6 months because it has 1 million entries" you can
say "Well, only generate the report for the last month".

My problem is I can not even generate a report for one month because I
generate a million entries in one month.

In conclusion:

#1 can phpOpenTracker's internals be improved to make retrieving data
faster?

#2 can a faster reporting tool be written?

I have no idea about #1 but I am willing to work on #2 if anyone has
ideas on makes a phpOpenTracker reporting tool fast.

Jean-Christian Imbeault



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