As well as the excellent suggestions above, I'd suggest archiving data from this table to reduce the table size (i.e. move historical results say past 6 months or whatever is relevant) to another table or database entirely. Realistically are clients wanting to see all historical data?, Could you calculate some coarser-grained aggregates as a background job (daily) and store in a new table?
Cheers, -Dan On Thu, Sep 17, 2009 at 4:15 PM, [email protected] <[email protected]> wrote: > Hi Greg, > > You could try turning on the slow query log ( > http://dev.mysql.com/doc/refman/5.4/en/slow-query-log.html ) and see if it > has anything to say. Note though that "The time to acquire the initial table > locks is not counted as execution time", so if Paul is right and its the > table type you're using that's the problem then it won't tell you about it. > > http://blog.mysqltuner.com/ is a useful place to start too, esp if it's not > table locking. > > Cheers, > > Andy > > > > --~--~---------~--~----~------------~-------~--~----~ NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected] -~----------~----~----~----~------~----~------~--~---
