The monitor observes the memory usage by non Analysis Services processes on the server, to ensure Total Memory Limit for Analysis Services is always available.
Knowledge Base article:
Summary
Memory usage on the server hosting SSAS instance may impact the health and performance of the server by competing for shared resources from which the instance must also make allocations. This can lead to exhaustion of available physical memory on the computer, which can force the operating system to map virtual memory to the page file on disk, orders of magnitude slower than physical memory. For any business critical applications dependent upon a SSAS instance, the server should be configured in such a way that other processes (e.g., anti-virus, disk defragmentation, other instances of SSAS or the SQL Server relational database engine, etc.) do not allocate excessive memory, leading to this circumstance.
Causes
The most common processes to significantly compete with SSAS instances for memory primarily include other instances of SSAS, SQL Server relational database engine, or other database servers, since these tend to be the most intensive consumers of memory hosted on the servers, where SSAS is also hosted. Sometimes non-database software may also heavily consume the memory. As such, memory considerations may frequently affect the configuration of a server.
Besides, the value of free unreserved memory (FreeUnreservedPercent parameter) may become negative. This parameter is calculated as follows: 100% of the total memory minus high memory usage by the instance (SSAS), and minus memory usage by other processes. The reasons may be:
Total Memory Limit parameter is set incorrectly in the configuration file
Total memory used by other processes and the preset limit for SSAS exceeds 100%
The Task Manager can be used to examine memory usage by various processes on the server. If instance(s) of SSAS (msmdsrv.exe) or SQL Server relational database engine (sqlservr.exe) consuming excessive memory, this is a simple way to identify their usage quickly, and, of course, it is also possible to see if other processes on the system are contributing to the condition. Subsequently, corrective actions (such as tuning memory usage of the instances by the SQL administrator, adding hardware, or reducing/dividing workload on the machine) may be devised accordingly.
Resolutions
Resolving issues of total server usage require the administrators to understand and consider numerous factors, including but not limited to workload requirements, user and job schedules, other scheduled processes on the server computer, and resources available. Actions to remediate excessive total memory allocations on the server computer may include any of the following actions:
Increase available physical memory on the server computer.
Decrease consumption by SSAS instance(s) or relational database instances by modifying design after reviewing SSAS Multidimensional Performance Guide, or contacting Microsoft support.
Decrease consumption by other processes through means specific to each of the processes, or by terminating those not required on the server.
Schedule jobs or reports on the affected instance(s) to avoid simultaneous workload during periods, when the server memory is excessively allocated.
Tune the configured thresholds for the alert to avoid the condition.
Disable the monitor entirely if memory usage is not a concern on the server.
SSAS: Other processes have allocated too much memory
The amount of memory prescribed by Total Memory Limit setting may be not available for SSAS, because other processes have allocated too much memory ({4} GB).
Total memory on the server: {2} GB
Total memory usage: {5} GB
Memory used by non-SSAS processes: {4} GB
Memory used by SSAS: {3} GB
SSAS Memory Limit Low: {6} GB ({7}\%)
SSAS Memory Limit High: {0} GB ({8}\%)
Home
