For the data warehouse, the key determinants are the size and complexity of the database queries. Conversely, for BOXI the key determinants are the number of data rows returned by a query and the number of pages of report results.
The main difficulty when sizing an ad-hoc reporting system is that you do not know in advance the mix of reports that your users will run, and how often they will run these reports. Bigger reports require more processing, while report frequency rises as the number of users increases.
We recommend that you use the current level of usage for iConsole standard reports as your baseline. However, a direct comparison with current usage levels may underestimate future usage levels. In particular:
Most BusinessObjects Enterprise reports for CA Data Protection are direct equivalents of iConsole standard reports. They generally run as fast as, or faster than, the iConsole standard reports. For this reason, your reviewers are likely to switch to BusinessObjects Enterprise reports and may run reports more frequently. In turn, this switch leads to an increase in the data warehouse workload.
Note: Certain BusinessObjects Enterprise reports for CA Data Protection are slower than their equivalent standard report, especially the Detailed Issue Report and the Compliance Audit Report. Such BusinessObjects Enterprise reports are slower because they run multiple queries to retrieve the necessary details.
A key advantage of BusinessObjects Enterprise is the ease with which users can create and publish custom reports. Such activity causes an increase in the data warehouse workload.
We also strongly recommend that you review any new reports created by your users. Verify that the new report definitions are 'efficient' and do not adversely affect data warehouse performance. You may also want to limit the number of users who are permitted to save custom reports in the InfoView Public Folder.
Note: Only members of the CA DLP Reports Author and CA DLP Reports Administrator BusinessObjects user groups can create new reports. Members of the CA DLP Reports Viewer group are not permitted to create new reports. (These user groups are created when you install the BusinessObjects Universe for CA Data Protection.)
Workload distribution over time is critical. We recommend that you limit the level of concurrent reporting activity during office hours to prevent other activity in the CA Data Protection CMS database from being adversely affected.
The optimum number of reports that can run concurrently at peak times depends on query performance.
The data warehouse handles most of the workload, so query performance is generally the limiting factor here.
Although the CA Data Protection data warehouse is fast for certain queries, significant workload is inevitable for queries that require complex row level security (RLS).
Use the BOXI scheduling functionality to alleviate workload issues. Monitor patterns of report usage and encourage your users to schedule their reports to run overnight. Scheduling spreads the workload over time and reduces the impact on the CA Data Protection CMS database while other users are online.
When you measure data warehouse performance, we recommend that you run a set of reports concurrently which are representative of your users’ reporting activity. Set up a BOXI object package containing multiple representative reports and create a schedule to run the package. While the reports are running, monitor the following items:
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|