MicroStrategy ONE
Performance Troubleshooting
Project Performance
You may notice a project that takes longer to load than others, or you may see the following error message in the server log file:
[DSS Engine] [Error]DSSSQLEngine: WARNING: Object cache MaxCacheCount setting (200) is too small relative to estimated schema size (461).
The project loading time involves retrieving a significant amount of data and can be time-consuming depending on the project's size, your hardware configuration, and your network. If a project takes a long time to load or you see the error message above, you can look at the following:
- Load at startup: During installation of MicroStrategy, did you select to have the project "Load at startup"? This option generally speeds subsequent requests for the project because much of the information necessary to load the project is cached on the server.
You can check whether your project is set to load at startup using the Intelligence Server Configuration Editor. (In Developer, right-click the project source and select Configure MicroStrategy Intelligence Server. Expand the Projects category, and then select General.)
- Maximum RAM usage for object cache: Depending on the size of your schema objects, you may need to raise the Maximum RAM usage (KBytes) setting. (To locate this setting: In Developer, right-click on the project and select Project Configuration. From the Caching category, select Objects.)
The error message shown above will contain an estimated schema size. This number should be multiplied by 10 and the result entered in the Maximum RAM usage setting. This setting may help optimize your project.
Raising the number for Maximum RAM usage may cause high memory use, which may cause your machine to experience problems. Be sure you understand the full ramifications of all settings before you make significant changes to them.
- Turn off diagnostic tracing: If you have tracing turned on, turn it off to ensure the project is loaded without logging any unnecessary information that can slow down performance. (In Developer, from the Tools menu, select Diagnostics. Click Help for details on the various tracing options.)