In order to bring you the best possible user experience, this site uses Javascript. If you are seeing this message, it is likely that the Javascript option in your browser is disabled. For optimal viewing of this site, please ensure that Javascript is enabled for your browser.
Login  |   On Demand  |   Home  |

Example Sizing
This section provides an example of how to size a BI system.
Size a BI system with the following requirements:
20 expected concurrent BI Portal users
A 50-GB ERP source database
Initially, three BI Modules required
This example shows a single-tier deployment in which one server holds all BI components.
Sizing Metric:
CPU – DWD/Scheduler
2 cores
CPU – Concurrent User Workload (Remote Portal Users)
20 concurrent users = 6 cores
CPU – BI Portal Webapp
1 core
CPU Total
6 + 1 = 7 cores
Max. (A,B) + C – This is a minimum requirement
RAM - DWD/Scheduler
Assume “Medium” Load – 8+ GB
RAM – BI Portal Webapp
2 GB
RAM – Concurrent User Workload (Remote Portal Users)
RAM - Total
8+ + 2 + 4 GB = 14 GB
As per RAM Sizing for DWD/Scheduler Component, the 4 GB extra is for the OS
Disk Sizing
Carry out initial approximate sizing to create an approximate estimate of the initial DW size based on ERP table data. See “Reference: Estimation of Initial Database Size”.
As a note, 500 GB is a recommended minimum but all new implementations should obtain disk sizing estimates using the referenced guidelines.
IO Subsystem
15 k rpm SAS disks
RAID 10 on a SAN/NAS device
Minimum of 6 disks (12 disks if using mirroring).
Again, depending on the estimated DW size, increase the number of disks in the RAID array.
Network Requirements
ERP-to-BI Server: Minimum of 3 MBps (Mega-bytes per second) bandwidth
Client-to-BI Portal: Minimum of 100 kbps (kilo-bytes per second) bandwidth per user
Ensure 1-Gbps network card minimum on DW server. For two-tier deployment, also ensure at least a 1-Gbps network connection between the DW server and the BI Portal webapp server.