25 Feb

Ninja tricks in top!

One of our senior MySQL DBAs, Mike Hamrick, wasn’t feeling well this week and so stayed home from the office. ┬áInstead of actually resting, produced this video about reading top output! ┬áI leave it to you all to watch and learn from our local tool tip pro.

And, feel better Mike!

Related posts from the blog:

  1. Introducing the Bluegecko MySQL Training AMI
    I created the Bluegecko MySQL training AMI as a MySQL sandbox that folks could use to learn things...
  2. OurSQL Episode 32: Backup tools you already have [Backup series #2]
    Show notes: Previous backup series podcast: Backup glossary [Backup series #1] Feedback: In the backup glossary we asked...
  3. Ignite MySQL at the MySQL Conference and Expo
    I’ll be giving a talk tonight at the Ignite MySQL! For those of you who don’t know about...
  4. Ignite MySQL at the MySQL Conference and Expo
    I’ll be giving a talk tonight at the Ignite MySQL! For those of you who don’t know about...
  5. Using SQL to create SQL (and other usefulness)
    Today, I had a task of modifying a slave to exclude (or if you want to say specifically...

One Response to “Ninja tricks in top!”

  1. Baron Schwartz 27. Feb, 2011 at 4:53 pm #

    Great video. I did not know about /proc/interrupts — that looks very useful for some troubleshooting tasks. I’ll add that to Aspersa’s collect tool :)

    Small correction: the load average doesn’t come from (R)unning processes, but rather (R)unnable processes (and those that are blocked on IO, which differs from most Unixes). When Mike said “the run queue” he was right — but processes that are on the run queue aren’t running, they are waiting for a CPU to be available. That’s why load average is a good indication of backlog.

Leave a Reply