Bug #45552 Performance schema: --performance_schema_max_mutex=1 gives no mutex waits events
| Submitted: | 17 Jun 2009 8:24 | Modified: | 18 Jun 2009 0:34 |
|---|---|---|---|
| Reporter: | Jørgen Austvik | Email Updates: | |
| Status: | Not a Bug | Impact on me: | |
| Category: | MySQL Server: Performance Schema | Severity: | S3 (Non-critical) |
| Version: | mysql-6.0-perfschema | OS: | Any |
| Assigned to: | Marc ALFF | CPU Architecture: | Any |
[17 Jun 2009 8:24]
Jørgen Austvik
[17 Jun 2009 10:14]
Sveta Smirnova
Thank you for the report. Verified as described.
[18 Jun 2009 0:34]
Marc ALFF
Sorry, this is not a bug. The test expected results are incorrect. --performance_schema_max_mutex=1 means that at most 1 mutex instance in the server will be instrumented. This instance should be visible in table MUTEX_INSTANCES. For this instrumented mutex to actually generate an event in EVENTS_WAITS_CURRENT / _HISTORY / _HISTORY_LONG, there must be a scenario where the server executes a query that cover the instrumented code: executing any query won't do. On top of that, if also only one thread is instrumented, because of --performance_schema_max_thread=1 then the server needs to execute: - the instrumented thread, not just any thread - against the instrumented mutex, not just any mutex for an event to be recorded. --performance_schema_max_mutex=1 does not mean expect one distinct wait of each mutex. Thanks for the report, closing as not a bug.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.053 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.