Have you taken a look at this Samuel?
http://www.mysql.com/products/tools/administrator/index.html
Check out the demo in the TRH corner.
May be of some use to you.
Regards
Keith
In theory, theory and practice are the same;
in practice they are not.
On Wed, 19 Apr 2006, Samuel Ziegler wrote:
> To: [EMAIL PROTECTED]
> From: Samuel Ziegler <[EMAIL PROTECTED]>
> Subject: Re: Per query DB stats... ideally for InnoDB
>
> Those functions do give useful information, but as you point out, the
> trick is associating that information with a specific query. For my
> use, there will most likely be other SQL activity going on at the same
> time which makes doing a 'SHOW ENGINE ...' before and after the query
> not very useful.
>
> Thanks for the pointers, however.
> - Sam
>
> On Wed, 2006-04-19 at 23:30 +0100, [EMAIL PROTECTED] wrote:
> > Is this of any use at all?
> >
> > From the 5.0.18 manual:
> >
> > 13.5.4.7. SHOW ENGINE Syntax
> >
> > SHOW ENGINE engine_name {LOGS | STATUS }
> >
> > SHOW ENGINE displays log or status information about
> > storage engines. The following statements currently are
> > supported:
> >
> > snip
> > SHOW ENGINE INNODB STATUS
> > (or SHOW INNODB STATUS)
> >
> > Both return alot of info on the InnoDB storage engine. Not
> > sure how to relate this to each SQL query though.
> >
> > may be of interest too:
> >
> > 13.5.4.16. SHOW PROCESSLIST Syntax
> >
> > SHOW [FULL] PROCESSLIST
> >
> > SHOW PROCESSLIST shows you which threads are running. You
> > can also get this information using the mysqladmin
> > processlist statement. If you have the SUPER privilege, you
> > can see all threads. Otherwise, you can see only your own
> > threads (that is, threads associated with the MySQL account
> > that you are using). See Section 13.5.5.3, KILL Syntax. If
> > you do not use the FULL keyword, only the first 100
> > characters of each statement are shown in the Info field.
> >
> > This statement is very useful if you get the too many
> > connections error message and want to find out what is going
> > on. MySQL reserves one extra connection to be used by
> > accounts that have the SUPER privilege, to ensure that
> > administrators should always be able to connect and check
> > the system (assuming that you are not giving this privilege
> > to all your users).
> >
> > Regards
> >
> > Keith
> >
> > In theory, theory and practice are the same;
> > in practice they are not.
> >
> > On Wed, 19 Apr 2006, Samuel Ziegler wrote:
> >
> > > To: [email protected]
> > > From: Samuel Ziegler <[EMAIL PROTECTED]>
> > > Subject: Per query DB stats... ideally for InnoDB
> > >
> > > Is there any way to retrieve per SQL query stats from MySQL?
> > > Specifically for my need, the ability to determine the amount of system
> > > resources required to perform the query, ie CPU, disk usage, etc...
> > >
> > > I poked through the docs & did some net searching, but couldn't find
> > > anything that I could use.
> > >
> > > I chatted with someone who thought that InnoDB had had some code added
> > > to it to start down this path, but that it wasn't exposed to the user
> > > level at all.
> > >
> > > An alternative would be a good method of determining the resource cost
> > > of a query though an examination of the explain data.
> > >
> > > Thanks!
> > > - Sam
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
