Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
None
-
MXS-SPRINT-265
Description
The memory accounting done currently only takes the core of MaxScale into account. The memory used by modules is not exposed which makes it difficult to evaluate how much memory is consumed by the modules. Adding in the API endpoints for tracking the memory usage would make it possible to determine where the memory is being used and it would also make the memory estimate closer to what's actually spent by the session.