[MDEV-27935] Enable performance_schema profiling for trx_rseg_t latch Created: 2022-02-24 Updated: 2022-03-14 Resolved: 2022-02-24 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Performance Schema, Storage Engine - InnoDB |
| Affects Version/s: | 10.6.3, 10.6 |
| Fix Version/s: | 10.6.8, 10.7.4, 10.8.3 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Krunal Bauskar | Assignee: | Marko Mäkelä |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Attachments: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| Description |
When I applied the said patch and enabled profiling trx_rseg_latch_key was 2nd hottest instrument from the InnoDB SE perspective.
|
| Comments |
| Comment by Krunal Bauskar [ 2022-02-24 ] |
|
PR submitted: https://github.com/MariaDB/server/pull/2032 |
| Comment by Marko Mäkelä [ 2022-02-24 ] |
|
Thank you, Krunal! The patch looks good to me. Can you please show the performance impact of this when performance_schema is available but globally disabled at runtime? |
| Comment by Marko Mäkelä [ 2022-02-24 ] |
|
I had intentionally removed the PERFORMANCE_SCHEMA instrumentation in |
| Comment by Krunal Bauskar [ 2022-02-24 ] |
|
@Marko, Please check the attached graph fro x86. There is no impact due to adding pfs support for the said latch. |