Make SHOW MUTEX STATUS more useful

Bug #582802 reported by Baron Schwartz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona patches
Won't Fix
Undecided
Unassigned

Bug Description

Can we make SHOW MUTEX STATUS more useful by default? As it currently is, it's just a good way to make your terminal scroll for 15 minutes.

mysql> SHOW MUTEX STATUS;
+-------------+------+----------+
| File | Line | OS_waits |
+-------------+------+----------+
| trx0trx.c | 147 | 0 |
| trx0trx.c | 147 | 0 |
| trx0trx.c | 147 | 0 |
| trx0trx.c | 147 | 0 |
| trx0trx.c | 147 | 0 |
| trx0trx.c | 147 | 0 |
| trx0trx.c | 147 | 0 |
| trx0trx.c | 147 | 0 |
| trx0trx.c | 147 | 0 |
| trx0trx.c | 147 | 0 |
| trx0trx.c | 147 | 0 |
| trx0trx.c | 147 | 0 |
| trx0trx.c | 147 | 0 |
... snip ....
| buf0buf.c | 498 | 0 |
| buf0buf.c | 498 | 0 |
| buf0buf.c | 498 | 0 |
| buf0buf.c | 498 | 0 |
| buf0buf.c | 498 | 0 |
| buf0buf.c | 498 | 0 |
| buf0buf.c | 498 | 0 |
| buf0buf.c | 498 | 0 |
| buf0buf.c | 498 | 0 |
| buf0buf.c | 498 | 0 |
| buf0buf.c | 498 | 0 |
| buf0buf.c | 498 | 0 |
| buf0buf.c | 498 | 0 |
| buf0buf.c | 498 | 0 |
| buf0buf.c | 498 | 0 |
| buf0buf.c | 498 | 0 |
| buf0buf.c | 498 | 0 |
| buf0buf.c | 498 | 0 |
| buf0buf.c | 498 | 0 |
| buf0buf.c | 498 | 0 |
| buf0buf.c | 498 | 0 |
| buf0buf.c | 498 | 0 |
| buf0buf.c | 498 | 0 |
| buf0buf.c | 498 | 0 |
| buf0buf.c | 498 | 0 |
...snip...
| buf0buf.c | 498 | 0 |
| buf0buf.c | 498 | 0 |
| buf0buf.c | 498 | 0 |
| buf0buf.c | 498 | 0 |
| buf0buf.c | 498 | 0 |
| buf0buf.c | 558 | 13908 |
| buf0buf.c | 556 | 233 |
| buf0buf.c | 552 | 232373 |
| buf0buf.c | 549 | 9926 |
| fil0fil.c | 1294 | 89451 |
| srv0start.c | 1211 | 0 |
| srv0start.c | 1204 | 0 |
| srv0start.c | 1182 | 0 |
| dict0mem.c | 90 | 0 |
| dict0mem.c | 90 | 0 |
| srv0srv.c | 962 | 2 |
| srv0srv.c | 959 | 13740566 |
| thr0loc.c | 232 | 163 |
| mem0pool.c | 204 | 0 |
| sync0sync.c | 1327 | 0 |
+-------------+------+----------+
3014975 rows in set (1.33 sec)

Can this be done in a hash table and pre-aggregated?

Revision history for this message
Yasufumi Kinoshita (yasufumi-kinoshita) wrote :

I think aggregating is non-sense... They are different mutex/lock. They cannot be compared with the other un-aggregated values.

Do you like "mutex status" of InnoDB Plugin or XtraDB?
It skips "0" items and block->mutex. It seems enough for me.

Revision history for this message
Peter Zaitsev (pz-percona) wrote : Re: [Bug 582802] Re: Make SHOW MUTEX STATUS more useful
Download full text (3.5 KiB)

Yasufumi,

Can we make it available like information_schema.table like other
information ?
In this case we can use group by if we want to aggregate it as well as other
things - for example we may want to find MAX() to see the hottest mutex of
the set etc.

On Thu, May 20, 2010 at 1:02 AM, Yasufumi Kinoshita <
<email address hidden>> wrote:

> I think aggregating is non-sense... They are different mutex/lock. They
> cannot be compared with the other un-aggregated values.
>
> Do you like "mutex status" of InnoDB Plugin or XtraDB?
> It skips "0" items and block->mutex. It seems enough for me.
>
> --
> Make SHOW MUTEX STATUS more useful
> https://bugs.launchpad.net/bugs/582802
> You received this bug notification because you are a member of Percona
> developers, which is the registrant for Percona patches.
>
> Status in Patches for MySQL by Percona: New
>
> Bug description:
> Can we make SHOW MUTEX STATUS more useful by default? As it currently is,
> it's just a good way to make your terminal scroll for 15 minutes.
>
> mysql> SHOW MUTEX STATUS;
> +-------------+------+----------+
> | File | Line | OS_waits |
> +-------------+------+----------+
> | trx0trx.c | 147 | 0 |
> | trx0trx.c | 147 | 0 |
> | trx0trx.c | 147 | 0 |
> | trx0trx.c | 147 | 0 |
> | trx0trx.c | 147 | 0 |
> | trx0trx.c | 147 | 0 |
> | trx0trx.c | 147 | 0 |
> | trx0trx.c | 147 | 0 |
> | trx0trx.c | 147 | 0 |
> | trx0trx.c | 147 | 0 |
> | trx0trx.c | 147 | 0 |
> | trx0trx.c | 147 | 0 |
> | trx0trx.c | 147 | 0 |
> ... snip ....
> | buf0buf.c | 498 | 0 |
> | buf0buf.c | 498 | 0 |
> | buf0buf.c | 498 | 0 |
> | buf0buf.c | 498 | 0 |
> | buf0buf.c | 498 | 0 |
> | buf0buf.c | 498 | 0 |
> | buf0buf.c | 498 | 0 |
> | buf0buf.c | 498 | 0 |
> | buf0buf.c | 498 | 0 |
> | buf0buf.c | 498 | 0 |
> | buf0buf.c | 498 | 0 |
> | buf0buf.c | 498 | 0 |
> | buf0buf.c | 498 | 0 |
> | buf0buf.c | 498 | 0 |
> | buf0buf.c | 498 | 0 |
> | buf0buf.c | 498 | 0 |
> | buf0buf.c | 498 | 0 |
> | buf0buf.c | 498 | 0 |
> | buf0buf.c | 498 | 0 |
> | buf0buf.c | 498 | 0 |
> | buf0buf.c | 498 | 0 |
> | buf0buf.c | 498 | 0 |
> | buf0buf.c | 498 | 0 |
> | buf0buf.c | 498 | 0 |
> | buf0buf.c | 498 | 0 |
> ...snip...
> | buf0buf.c | 498 | 0 |
> | buf0buf.c | 498 | 0 |
> | buf0buf.c | 498 | 0 |
> | buf0buf.c | 498 | 0 |
> | buf0buf.c | 498 | 0 |
> | buf0buf.c | 558 | 13908 |
> | buf0buf.c | 556 | 233 |
> | buf0buf.c | 552 | 232373 |
> | buf0buf.c | 549 | 9926 |
> | fil0fil.c | 1294 | 89451 |
> | srv0start.c | 1211 | 0 |
> | srv0start.c | 1204 | 0 |
> | srv0start.c | 1182 | 0 |
> | dict0mem.c | 90 | 0 |
> | dict0mem.c | 90 | 0 |
> | srv0srv.c | 962 | 2 |
> | srv0srv.c | 959 | 13740566 |
> | thr0loc.c...

Read more...

Revision history for this message
Stewart Smith (stewart) wrote :

I think we have better things in Percona Server now? Is this still relevant at all? If so, let's reopen against percona-server.

Changed in percona-patches:
status: New → Won't Fix
Revision history for this message
Baron Schwartz (baron-xaprb) wrote :

I think having a MUTEX_STATUS I_S table would be an improvement over
the SHOW command. I'm not sure this is done by any other Percona
Server enhancements at the moment.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.