BI Hardware Sizing?
One of our recent discussion with a colleague & a client of mine resulted in this we brainstormed on what sizing is & what is the best methodology to achieve apt sizing for an OBIEE Hardware Environment.
I know there are big players like IBM with their Sizing & vending strategies & questionnaires to make it complex but here is a basic understanding.
A sizing is an approximation of the hardware resources required to support a specific software implementation.
It is important to understand that “sizing” the hardware for each customer’s Oracle Business Intelligence Enterprise Edition implementation is an iterative process, which may be refined and repeated a number of times. If you are in the early stages of planning, you will probably have limited information about your planned environment. In this case, we can complete the sizing estimate with general information about your Oracle Business Intelligence Enterprise Edition applications users.
The steps that we need to keep in mind to develop the right sizing is to figure out the right thorough put that may be needed when our System Goes Live for Production to the Max number of users,
Throughput is the maximum number of queries & data load that our BI Presentation Services, BI Server, BI Scheduler, The Database Server Machine can handle for optimal performance there a quite a few tools out there which can be used to determine the thorough put
The thorough put is determined in a Firewall free demilitarized zone.
Thorough put is The amount of data that is being accessed by queries hitting the system at peak time, in conjunction with the acceptable response time. You may be able to use throughput numbers and experience from an existing application to estimate the required throughput.
As a rule of thumb we can use the following formula to determine the CPU sizing, Ram Memory, Disks
-
The Number of CPU’s = ( The Max Throughput / 200 ) In MB
-
Memory In GB = 2 Times Number of CPU’s
-
System Throughput In MB / Individual Disk Controller’s Throughput Gives Us The Number of Disk Controller’s
