Archive for the ‘mytop’ tag
This release is part of the unstable 1.5 branch. Its features will ultimately go into the stable 1.6 branch. You can download it from the innotop-devel package.
The major change is a new Command Summary’ mode (switch to this mode with the ‘C’ key) that’s similar to mytop’s ‘c’ mode. It shows you the relative size of variables from SHOW STATUS and SHOW VARIABLES. Here’s a sample:
Command Summary (? for help) localhost, 25+07:16:43, 2.45 QPS, 3 thd, 5.0.40 _____________________ Command Summary _____________________ Name Value Pct Last Incr Pct Select_scan 3244858 69.89% 2 100.00% Select_range 1354177 29.17% 0 0.00% Select_full_join 39479 0.85% 0 0.00% Select_full_range_join 4097 0.09% 0 0.00% Select_range_check 0 0.00% 0 0.00%
The default is to show the
Com_* variables, but I’ve used a different prefix to illustrate that you can view any variables you want. You just choose the prefix. Useful ones are
Sort_. This gives you instant insight into the kind of work your server is doing. You can see in the sample above that the kinds of joins the server does is healthily balanced towards scans and ranges on the first table. The server does very few full joins, full range joins, and range-check query plans (this is good).
The example shows one server, as you can see by the first line. Naturally, you can monitor many servers in aggregate, and it’s configured to do this by default if you’re watching more than one server. However, there’s a bug in the percentage columns when you do that (the Value columns are accurate when aggregated). I have a fix in mind for that, which will also fix many other things that cause me (and you) too much work when customizing innotop. But that’ll come later. I feel this is good enough for now, since the main use for this mode is when you’re just trying to familiarize yourself with a server, perhaps at a consulting job, or when reading someone’s tuning tutorial or the like.
Version 1.4.3 of the innotop MySQL and InnoDB monitor is out. This release fixes some minor bugs and feature annoyances, and at last innotop has thorough documentation, available online!
Here’s what’s new:
- Added standard –version command-line option
- Changed colors to cyan instead of blue; more visible on dark terminals.
- Added information to the filter-choosing dialog.
- Added column auto-completion when entering a filter expression.
- Changed Term::ReadKey from optional to mandatory.
- Clarified username in password prompting.
- Ten thousand words of documentation! Documentation is embedded in innotop, installed as a man page, and available online.
- innotop crashed in W mode when InnoDB status data was truncated.
- innotop didn’t display errors in tables if debug was enabled.
- The colored() subroutine wasn’t being created in non-interactive mode.
- Don’t prompt to save password except the first time.
I don’t know how much time I’ll get to put into this in the coming months, but there’s already a lot of half-finished functionality in the Subversion repository, including the ability to write innotop plugins. If you’re interested, the code is in the trunk and in various branches.
Hopefully I’ll get time to work on some of that before the year is out.