Performance analysis

Administrators can use this analysis area to understand what effect the server and project governing settings and usage patterns have on the system.

The Performance Analysis folder has several reports and two folders, each with its own related area of analysis:

• Cube advisor
• Performance monitoring analysis

The Performance Analysis folder in Enterprise Manager has reports that measure such metrics as average job execution time and other job performance trends, cache analysis, longest executing reports, and so on.

Report name	Function
40. System Performance Trends	Analyzes system performance over time using your choice of metrics. This report is prompted on time and on methods of analysis.
41. Cache Analysis	Analyzes the effectiveness of caching on the system. This report is prompted on time, indicator, and the top number of report processing metrics. The project is in the report's page by area.
42. Job Performance Trend	Analyzes daily and weekly trends in report requests and job performance. This report is prompted on time.
43. Top 10 Database Tables	Lists the top 10 most accessed database tables per project and how many jobs access those tables. This report is prompted on time.
44. Warehouse Tables Accessed	Provides a count of the warehouse tables and columns accessed, by type of SQL clause. This report is prompted on time.
45. User Data Request Performance Breakdown	Provides insight into how users are using the monitored projects and Intelligence Server and looks at the user experience for the monitored systems regarding the data requested. This report is prompted on time.
46. Cache Analysis (End-to-End)	Provides average wait times and number of user requests via MicroStrategy Mobile that hit the application cache—which are usually from using the Back button—device cache, server cache, or no cache. This report is prompted on time.
47. Network Type Analysis (End-to-End)	Provides average wait times and number of user requests, categorized by the type of network from which the requests originated. This report is prompted on time.
48. For Capacity Planning Team (Number of Jobs)	Provides information about how many jobs were executed, with numbers of hits for caches and Intelligent Cubes. This report is prompted on time.
49. For Capacity Planning Team (User/Session Concurrency)	Provides information by day, hour, and connection source of numbers of users and sessions. This report is prompted on time.
50. For Capacity Planning Team (Document Executions)	Provides information by day and hour of how many documents were executed and the average number of reports per document. This report is prompted on time.
51.1 For EA Team (Report Processing Analysis - Job Based)	Provides information about how long report job steps took for a report you select. This report is filtered by day, hour, and minute.
51.2 For EA Team (Document Processing Analysis - Job Based)	Provides information about how long document job steps took for a document you select. This report is filtered by day, hour, minute, and document.
52.1 For EA Team (Report Processing Analysis - Time Based)	Provides information about how long report job steps took for reports that were running at a selected time. This report is filtered by day, hour, and minute.
52.2 For EA Team (Document Processing Analysis - Time Based)	Provides information about how long job steps took for documents that were running at a selected time. This report is filtered by day, hour, and minute.
53. For EA Team (Performance Monitor)	Dashboard with performance monitor trends and execution times for jobs executed at a selected time.
53. For EA Team (Performance Monitor) (HTML 5)	Dashboard with performance monitor trends and execution times for jobs executed at a selected time.
53.1 For EA Team (Dataset: Document Report Execution Analysis)	A dataset report for the above performance monitor dashboards showing document and report execution times for jobs running at the selected time.
53.2. For EA Team (Dataset: Performance Counter Trend)	A dataset graph report for the above performance monitor dashboards showing trends in the selected performance counter such as percent of CPU time, total in-use memory, and so on.

Two reports from this analysis area are presented in detail below. These sample reports have been selected as representative reports of the analysis area; the details and options suggested for the sample reports can often be used on other reports in the same or related analysis areas.

Sample report: Cache Analysis

This report provides a comprehensive analysis of report caching in the system. A good caching strategy can significantly improve system performance. This report is prompted on time and on the job type you want to analyze, and you can select the number of top report jobs you want to see data for.

Usage scenario

You can use this report to analyze the cache hit ratios for certain reports; typically, these are the most frequently requested or most resource-intensive reports. You can also determine whether prompted reports should be set up to create a cache by analyzing whether prompted reports are hitting the cache regularly.

Report details

• To analyze the cache hit ratios for element load jobs, select Element Browsing Job at the prompt for the indicator filter. Be sure to remove the Report attribute from the report because Element browsing jobs are ad hoc and do not map to any existing report in the metadata. This can give you insight into tuning element-related project settings. To make changes to the project settings, in Developer, right-click the project name, select Project Configuration, expand Caching, expand Auxiliary Caches, and select Elements. For detailed information about these settings, click Help.
• To analyze the cache hit ratios for prompted jobs, select Prompted jobs at the prompt. This can give you insight into tuning advanced report-related project settings. To make changes to the project settings, in Developer, right-click the project name, select Project Configuration, expand Caching, expand Result Caches, and select Creation (to specify whether and how caches are created), Storage (to specify cache memory usage), or Maintenance (to specify cache expiration, or to purge caches). For detailed information about these settings, click Help.

Sample report: Warehouse Tables Accessed

This report provides a count of the number of warehouse tables and columns accessed in various SQL clauses. This report is prompted on time.

Usage scenario

You can use this report to gain insights into database tuning by determining which warehouse tables and columns are accessed in the various SQL clauses, such as SELECT, WHERE, and so on. This information can help you determine where database tuning can be adjusted to improve overall query and reporting performance of your MicroStrategy project.

For example, columns that are frequently accessed in the WHERE clause are good candidates for indexing.

Cube advisor

The reports in this analysis area give an overview of database execution statistics for report requests. They provide a picture of how measures such as report execution times are affected if reports are run against Intelligent Cubes rather than the data warehouse.

You can use the Database Execution Time of Reports report with Cube Advisor to provide data on the performance benefits of potential Intelligent Cubes, such as any decrease in the time required to execute SQL statements and the number of users that would be affected by the recommended Intelligent Cubes. For information on this report's contents and steps for exporting it and importing into Cube Advisor, see the Dynamic Sourcing chapter in the In-memory Analytics Help.

Report name	Function
46. Report Object Listing	Provides analysis of the attributes and metrics in a report. This report is prompted on report.
47. Projected Cube Execution Time of Reports	Projects the execution times of report jobs if they were to hit an Intelligent Cube. This report is prompted on time and on report.
48. Database Execution Time of Reports	Provides database execution statistics for report requests. This report is prompted on time and on project. You can export this report as an Excel file and then import it to the Cube Advisor.

Performance monitoring analysis

The reports in this analysis area measure Intelligence Server performance, as recorded by the Diagnostics and Performance Logging Tool's Performance Monitors. For information about enabling these counters, or other uses of the Diagnostics and Performance Logging Tool, see the System Administration Help.

Report name	Function
92. Performance Monitor Report	Lists the Performance Monitor Counters recorded in project statistics, and their values, over a selected time. This report is prompted on time and on what counters are recorded in the Enterprise Manager warehouse.
93. Performance vs. Governing Settings	Provides general performance analysis against Intelligence Server governing settings over a selected time. To achieve maximum flexibility in this report, make sure that the following performance counters are logged in the Diagnostics and Performance Logging Tool: • Executing Reports • Memory Used by Report Caches • Number of Report Caches • Open Project Sessions • Open Sessions
94. Report Performance against Governing	Provides an analysis of report performance against Intelligence Server governing settings over a selected time. To achieve maximum flexibility in this report, make sure that the following Performance Counters are logged in the Diagnostics and Performance Logging Tool: • Executing Reports • Memory Used by Report Caches • Number of Report Caches
95. User Performance against Governing	Provides an analysis of performance per user against Intelligence Server governing settings over a selected time. To achieve maximum flexibility in this report, make sure that the following performance counters are logged in the Diagnostics and Performance Logging Tool: • Open Project Sessions • Open Sessions
96. Delivery Performance against Governing	Provides an analysis of performance per subscription delivery against Intelligence Server governing settings over a selected time.