[MXS-4725] Investigate low-impact profiling options Created: 2023-08-21 Updated: 2023-09-15 Resolved: 2023-09-05 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Core |
| Affects Version/s: | None |
| Fix Version/s: | 23.08.1 |
| Type: | Task | Priority: | Major |
| Reporter: | markus makela | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Sprint: | MXS-SPRINT-189, MXS-SPRINT-190 |
| Description |
|
Evaluate the available tools for profiling MaxScale on-site in situations where the overhead of "brute-force" GDB profiling is too much. |
| Comments |
| Comment by markus makela [ 2023-09-05 ] |
|
Added a new maxctrl debug stacktrace command that can be used to generate a stacktrace of all threads as well as profile the performance of MaxScale if used with the --duration option. |