MicroStrategy - Performance


https://lw.microstrategy.com/msdz/MSDL/900/docs/Displaying_MicroStrategy_Intelligence_Server_statistics.htm - performance monitoring (this is one way for us to get performance statistics out of MSTR and integrate them into another monitoring system like Nagios)


What do I need to do?

  1. Set up Enterprise Manager
  2. Read various chapters in the System Administration Guide

How can we use Integrity Manager to automate performance testing?

You can use Integrity Manager to automate your performance testing. Integrity Manager can record how long it takes to execute a given report or document. It can also execute the reports or documents multiple times in the same test and record the time for each execution cycle, to get a better idea of the average Intelligence Server performance time.

A single instance of Integrity Manager can execute a performance test that duplicates the effect of a single user running multiple reports. This is suitable for load testing. If you are performing stress testing or capacity testing, you may need to distribute the load among multiple user sessions. To do this, you must run several instances of Integrity Manager, each executing a performance test.

How can we use scheduled reports for performance testing?

If your system includes Distribution Services or Narrowcast Server, you can schedule reports and documents to execute at specified times. These scheduled executions can use up to half of Intelligence Server’s resources, and thus are usually scheduled to run at off-peak times.

For email deliveries, ensure that the appropriate Transmitter object definition is configured so that end users are not disrupted by test emails. All emails delivered as part of a test should be delivered to files.

The advantages of this type of test are that it is relatively easy to configure, and it simulates a production workload. However, it only tests Intelligence Server, not MicroStrategy Web Server. As such it may offer an incomplete picture of your system’s performance.

How can we do performance testing that includes MSTR Web?

Use tools that are standard for web performance testing such as Load Runner, htperf, or other online services that can do performance test from various part of the world.

Borland SilkPerformer, HP LoadRunner, or Apache JMeter, can be used to automate the performance testing process. These tools generally require the recording of a set of user actions. These actions are then parameterized and automatically executed multiple times, simulating user actions and generating load on Intelligence Server and MicroStrategy Web Server.

An all-hands test consists of many users logging into the test system at the same time and performing the actions they normally perform in the production environment, such as creating, manipulating, and executing reports and documents. The test should last for at least an hour to put a proper stress on the system.

An all-hands test has the advantage of doubling as a business acceptance test, since it allows end users to provide feedback on the system’s performance. It also provides an accurate test because the users are performing normal user actions. However, it requires a great deal of communication with the end users throughout the process, and a realistic load on the server depends on a high level of end user participation.

How can we use Windows Performance Monitor?

The Windows Performance Monitor is not part of MicroStrategy, but can be useful for monitoring your system resources. For information about using the Windows Performance Monitor to monitor how MicroStrategy system components are using system resources, see Managing system memory and resources: Windows Performance Monitor, page 375 (System Administration Guide)

How can we detect that the Intelligence server is being restarted due to memory issue?

  1. Open up the DSSErrors.log file and search for "depleted".
  2. Look at the Windows NT Event Viewer. You should see something like: 'DSSServerMemoryDepletionHandler(): Memory usage reaches maximum limit, the server is shutting down.'
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License