maria-developers team mailing list archive

[worklog-noreply@xxxxxxxxxxxx]

-----------------------------------------------------------------------
                              WORKLOG TASK
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
TASK...........: MySQL Wait Interface
CREATION DATE..: Wed, 10 Mar 2010, 10:53
SUPERVISOR.....: Bothorsen
IMPLEMENTOR....: 
COPIES TO......: 
CATEGORY.......: Client-BackLog
TASK ID........: 102 (http://askmonty.org/worklog/?tid=102)
VERSION........: Benchmarks-3.0
STATUS.........: Un-Assigned
PRIORITY.......: 60
WORKED HOURS...: 0
ESTIMATE.......: 0 (hours remain)
ORIG. ESTIMATE.: 0

PROGRESS NOTES:



DESCRIPTION:

What lacks in MySQL is something similar like the Oracle Wait Interface. The
basic idea is, that every connection/thread (and the whole system) shows (on
request) where it spent how much time doing what.

They implemented the wait interface (which is possibly a sub-set of Sun's
dtrace) where you can see where you loose your time.

Marc Callaghan and Baron Schwartz blogged in this direction recently:

http://www.xaprb.com/blog/2009/11/07/a-review-of-optimizing-oracle-performance-by-cary-millsap/
http://www.facebook.com/note.php?note_id=355839540932

Good sources to start with:
http://www.amazon.com/Oracle-Wait-Interface-Performance-Diagnostics/dp/007222729X
http://books.google.ch/books?id=14OmJzfCfXMC&pg=PA6&lpg=PA6&dq=owi+is+a+performance+tracking+methodology&source=bl&ots=KN625PxI3p&sig=C_jeduD3UqcMp9ihaaHcucf1AV0&hl=en&ei=BXmXS-nbNM6psAaj0IzbCA&sa=X&oi=book_result&ct=result&resnum=1&ved=0CAoQ6AEwAA#v=onepage&q=owi%20is%20a%20performance%20tracking%20methodology&f=false
http://www.oracle.com/technology/books/pdfs/sample%20chapter%202729x.pdf
http://www.amazon.com/Optimizing-Oracle-Performance-Cary-Millsap/dp/059600527X


ESTIMATED WORK TIME

ESTIMATED COMPLETION DATE
-----------------------------------------------------------------------
WorkLog (v3.5.9)