On Tue, Jan 26, 2010 at 8:11 PM, Stewart Smith <[email protected]> wrote: > On Tue, Jan 26, 2010 at 07:15:29PM -0800, MARK CALLAGHAN wrote: >> > I think rdtsc is not at all a good idea in this modern world. >> >> Jay's original post was about incorporating support for fast timers. >> You go from that to rdtsc to the performance schema to using something >> that is far more complex. I just want a cheaper way to read the wall >> clock time (cheaper than gettimeofday). > > Did go out on a bit of a tangent there..... > > you're basically wanting a more free way of "how long did this query > take" ?
Right now we use it for several global counters displayed in SHOW STATUS: * #seconds in ha_innobase::records_in_range * #seconds in parser * #seconds in post-parse but pre-execution * #seconds in execution * #seconds running slave SQL * timing IO operations in InnoDB for information_schema.table_statistics More uses will come when we do more top-down monitoring per-account (information_schema.user_statistics). -- Mark Callaghan [email protected] _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
