> Minor correction: The post i point to is about the slow log, but I presume
> also relevant for the general log. And the good comments I mentioned come in
> the followup posting at http://www.bitbybit.dk/carsten/blog/?p=116
>
> / Carsten
Thanks Carsten, I read the comments and Sheeri mentions mys
Well, first thing I'd do, is symlink the log table files onto a separate set
of spindles. No use bogging the main data spindles down with logwrites.
On Tue, Apr 20, 2010 at 5:33 PM, Carsten Pedersen wrote:
> Carsten Pedersen skrev:
>
> Jim Lyons skrev:
>>
>>> Has anyone tried using the log_out
Carsten Pedersen skrev:
Jim Lyons skrev:
Has anyone tried using the log_output option in mysql 5.1 to have the
general log put into a table and not a flat file? I used it for a while
before having to downgrade back to 5.0 but thought it was a great
idea. I'm
curious to see if anyone feels it
Jim Lyons skrev:
Has anyone tried using the log_output option in mysql 5.1 to have the
general log put into a table and not a flat file? I used it for a while
before having to downgrade back to 5.0 but thought it was a great idea. I'm
curious to see if anyone feels it helps analysis.
I tried
Hi Imran,
you can have a look at mysqldumpslow utility to analyze the data..
Thanks
Anand
On Tue, Apr 20, 2010 at 5:48 PM, Jim Lyons wrote:
> Has anyone tried using the log_output option in mysql 5.1 to have the
> general log put into a table and not a flat file? I used it for a while
> befor
Has anyone tried using the log_output option in mysql 5.1 to have the
general log put into a table and not a flat file? I used it for a while
before having to downgrade back to 5.0 but thought it was a great idea. I'm
curious to see if anyone feels it helps analysis.
On Tue, Apr 20, 2010 at 6:02
Maybe one of the maatkit tools will do it, but I tend to graph that kind of
data live in Munin from the internal counters.
On Tue, Apr 20, 2010 at 1:02 PM, Imran Chaudhry wrote:
> I have 7 days worth of general log data totalling 4.4GB.
>
> I want to analyze this data to get:
>
> a) queries per
