mysqlguy.net

*Sigh*, well I won't be making it out to the conference this year:  My wife is due any day now with our third child.  Scheduling to fly to California next week just doesn't seem like it falls under the category of "supporting my wife."  

I recently got this email from a reader on my site and since I haven't posted for a while, I thought it might be a good discussion:

Jay,

I've been reading your site and had a question that you might have good insight for.  

I'm working on a high-traffic website that includes forums.  All the code is custom PHP, including the forums, simply because the PHP BB software out there doesn't scale as large and as well as I wanted.  I've implemented heavy memcached usage, distributed databases, etc. to handle any level of growth we may hit.

I spent some time going through the source the other day in order to try to understand the difference between these SHOW STATUS variables in 5.x:

A new version of myq_gadgets has been released and you can download it here.

Version 0.0.9 -
    - Documented new reports in README
    - Updated 'thds' column in the 'cttf' report to read 'crtd' instead.
Version 0.0.8 -
    - Added a bunch more innodb reports, looking for the good stuff.
Version 0.0.7 -
    - Added an 'innodb' mode to myq_status to support 5.0+ STATUS variables.
      'myq_innodb_status' continues to handle SHOW INNODB STATUS output,
      mostly for 4.1 and earlier.
    - Beefed up the format_memory function to use recursion to determine the
      appropriate output multiplier (tera, giga, mega, kilo, etc.)

I haven't gotten any responses to my question from Friday, so I figured I'd post a more direct question: