BOXI CPU SAP Units
These Export Sizing guidelines refer to BOXI CPU SAP units. These are standardized units of CPU power used by SAP to rate hardware. CPU SAP Units are measured as 1 unit per single core CPU. For a multi-core CPU, they are measured as 1 for the first core and 0.5 for subsequent cores (so 2.5 for a 4 core CPU.)
When sizing the BOXI server, we recommend that you leave one processor core unallocated for use by the OS.
This is the parent host service visible as a Windows service
The SIA requires 350MB memory and negligible CPU.
A single CMS supports up to 600 concurrent users and up to 500 concurrent object requests.
The CMS requires negligible CPU and 30-300MB of memory.
You can specify the maximum number of objects that the CMS stores in its memory cache by setting the maxobjectsincache command line parameter. See the BOXI 3.1 Administrators Guide for details.
Disk space requirements are associated with the BusinessObjects CMS database; see below.
The workload on this database typically comprises individual Reads and Writes of metadata (such as pointer references to blob files). Therefore, this database typically has minimal CPU or I/O requirements unless you have a very large number of active concurrent CMS users.
The database size depends on the number of objects (such as users or documents). In general, 100MB of database disk space can store 30,000 objects. For example, 30,000 objects equates to 100 users each with 15 reports, and with each report having 20 historic instances.
The FRS requires negligible memory or CPU requirements. It does require disk Input/Output.
To calculate FRS disk space requirements, multiply the following:
Average report size * Number of reports * Number of stored report history instances
Note: Small, one page reports are typically around 100KB, while major 100 page reports can be around 20MB.
FRS directory locations must use SAN/NAS devices for performance and redundancy.
If you want high performance, you can physically separate the FRS Input and Output folders and use separate disk controllers. Alternatively, you can move the Output FRS process to a dedicated server.
Note: You can configure multiple FRS processes. This provides failover redundancy, but it does not yield performance gains.
The repository search engine requires 500MB memory.
It supports 25 concurrent users per CPU unit. If you anticipate low concurrent usage, the CPU requirement is negligible.
Disk space requirements are approximately the same as for the FRS.
These services require 500MB memory and negligible CPU.
Disk space requirements are associated with the BusinessObjects audit database; see below.
Audit log files are periodically batch loaded to the BusinessObjects audit database. There is minimal additional workload associated with loading the audit data.
The database size varies considerably. It depends on the auditing level, the number of users, and the frequency of auditing activity. For example, 6 months of rolling audit history for 100 users requires approximately 100MB of disk space.
Running audit reports against a very large historic audit database places inense load on the database in short bursts. As a reporting database, we recommend that you do not locate this database on the BOXI server.
Allow between 1.8GB and 2GB memory for each WebI service. If you anticipate very large reports (say, 1000 pages), we recommend that you allow 2GB.
Allow one BOXI CPU SAP unit per WebI service process.
A single WebI service process typically supports up to 25 WebI documents concurrently.
The WebI service is critical. If a several large reports are processed concurrently, the total memory requirements may overwhelm the 2GB limit for a single WebI service. You must therefore distribute the workload by adding more WebI services. Indeed, we recommend that you have a minimum of two WebI services running for redundancy puropses and to help throughput. You create new servers and services in the Servers section of the Central Management Console (CMC).
Note: If a WebI report is rendered to PDF or Excel format, the workload on the WebI service occurs when the report is rendered, not when the report is viewed. For this reason, we recommend that users schedule reports torun during off-peak periods.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|