{question}
What accounts for the difference in Used Memory for a workspace between the SingleStore Portal and the Memory Monitoring dashboards?
{question}
{answer}
In the SingleStore portal, the total memory utilization for a specific workspace can be viewed under the Deployment -> Workspaces section below. However, this figure does not align with the overall memory usage displayed in the monitoring dashboards. This article thoroughly explores this discrepancy to clarify this behavior:
As observed above, there is a difference in the total memory: 14.1GB in the portal compared to 35.2GB in the memory dashboard. One of the main reasons for this discrepancy is that the monitoring dashboard provides a consolidated view of DDL, DML, and DML-Processing components of the workspace group, while the portal displays only the DML-processing memory. Once this filter is applied to the dashboard, the total memory aligns with that in the portal:
Here, however, there is a difference in the memory used (4.0GB on the dashboard vs. 1.9GB in the portal). This difference arises because the portal UI displays memory usage as a combination of Data, Other, and Query. Therefore, the memory usage is as follows:
Workspace memory use(portal) = Memory used by (Data + Query + Other)
Referring to the example above, the total memory usage is approximately 1.9 GB, which encompasses Data, Other, and Query usage as reported in the dashboard.
The additional memory displayed in the monitoring dashboards and the portal UI represents the reserved memory. Reserved memory refers to the memory already allocated to the SingleStore process by the operating system. This pre-allocated memory enables the SingleStore process to access it directly, bypassing repeated memory fetches from the operating system, which enhances performance and efficiency.
{answer}