[MXS-2211] Maxadmin 2.2 performance tuning documentation is wrong Created: 2018-12-05  Updated: 2020-03-27  Resolved: 2020-03-02

Status: Closed
Project: MariaDB MaxScale
Component/s: Documentation, maxadmin
Affects Version/s: 2.2.17
Fix Version/s: 2.5.0

Type: Bug Priority: Minor
Reporter: Mikko Mensonen Assignee: Johan Wikman
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MXS-2904 Document MaxScale performance tuning Closed

 Description   

As discussed here, the performance tuning section in MaxScale 2.2 documentation makes references to maxadmin statistics outputs that are no longer present and hints at adjusting parameters that no longer matter.

Suggest removing the outdated references and replacing them with up-to-date guidelines as to how performance of MaxScale should be observed, which metrics are relevant and how MaxScale should be tuned (if at all) to best take advantage of the OS resources.



 Comments   
Comment by markus makela [ 2020-03-02 ]

Since MaxAdmin has been removed in 2.5, this bug is no longer relevant there. I've created MXS-2904 for documenting best practices for OS and MaxScale tuning.

Generated at Thu Feb 08 04:12:29 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.