It would be relatively straightforward to associate all memory allocations made while routing, with the session on behalf of which the memory allocation is made. That would make it possible to track how much memory a particular session consumes and how the memory consumption evolves over time. With some additional work it would also be possible to track which module - protocol, filter, router, etc. - is responsible for performing the memory allocation.

In 22.08 there will be slightly more information available regarding the memory usage. maxctrl show session will return the following:

├───────────────────┼──────────────────────────────────┤

│ Memory            │ {                                │

│                   │     "connection_buffers": 67226, │

│                   │     "last_queries": 0,           │

│                   │     "session_history": 774,      │

│                   │     "total": 68000,              │

│                   │     "variables": 0               │

│                   │ }                                │

└───────────────────┴──────────────────────────────────┘

This does not represent the total amount of memory use by a particular session, but provides figures that can be used for detecting anomalous behavior. The total field is currently simply the sum of all fields, and it is shown by maxctrl list sessions:

┌────┬───────┬───────────┬──────────────────────────┬──────┬─────────┬────────┐

│ Id │ User  │ Host      │ Connected                │ Idle │ Service │ Memory │

├────┼───────┼───────────┼──────────────────────────┼──────┼─────────┼────────┤

│ 1  │ johan │ 127.0.0.1 │ Thu Jun 30 15:44:29 2022 │ 305  │ RWS     │ 68000  │

└────┴───────┴───────────┴──────────────────────────┴──────┴─────────┴────────┘

Hi Johan, can we also show which session or query is consuming more memory?

Alert in the GUI with Critical/Warning/Notice in the GUI and through auto mail alert would be a good and it will be very useful feature for us.

naresh.chandra@copart.com Please create a separate feature request for that.

This is but the first step on this path. To be able to report the memory usage in greater detail, some architectural changes are needed and they are not possible to make in 22.08.

Sure Johan, thanks for the update.