Monitoring the OLAP Service

If you have multiple databases running, you can distinguish the processes by checking the command line in Task Manager. The ID of the resource, database name, and tenant are part of the command line and can be mapped to the database that you want to monitor.

OLAP is an in-memory database and delivers the best performance if all memory required by the server process is in the RAM. If the process memory is moved out to the page file, the performance will be slowed down.

To check the memory usage of a database process, you can check the commit size or private bytes of the process. This represents the memory allocated by OLAP. If you are using the Process Explorer from Microsoft Windows SysInternals, you can check for the peak private bytes which provides the maximum since the start of the database.

Use Task Manager to check the memory load on the machine. If the Committed value is higher than the RAM in the machine, it is overloaded. This number should be well under the amount of RAM on the machine.