I'm sure slow logging will be fine in this instance - we're not talking data warehousing or batch processessing here. :P
~ C -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of ctx2002 Sent: Thursday, 17 September 2009 5:08 p.m. To: NZ PHP Users Group Subject: [phpug] Re: [OT] Large Database Table Problems logging slow query is not a good idea, some time it misleading. also logging database query on big Traffic site probably will slow down IO (but i am not very sure about this) for example: one query take 1 hour to run, but only run for once a month, an other query takes 1 second to run , but it will be runned 1M time a day. that one hour query certainly not slow, but it will be log into slow query log. and that 1 second query will not be logged. regards, On Sep 17, 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] -~----------~----~----~----~------~----~------~--~---
