BWA 7.00: Sizing figure
[Accelerator] [BIA] [BWA] [memory consumptio] [overload] [Quicksizer] [sizing]
Related:
- BIA 7.00: reduce amount of parallel queriesSymptom You experience a high memory consumption on some or...
- BWA 7.00: Indexing fails due to GPFS issueSymptom Filling, rollup or changerun of BWA indexes fails Other...
- BWA 7.00: Analyzing write performanceSymptom You find that indexing in SAP NetWeaver BW Accelerator...
- BWA 7.00: Optimal settings for Revision 50 or laterSymptom You want to apply the optimal settings for SAP...
- BWA 7.00: Revision 52Symptom Update to BIA 7.00 Revision 52 Other terms Update,...
- SAP BusinessObjects Explorer Performance & ReliabilitySymptom SAP Note 1366180 “SAP BusinessObjects Explorer PERFORMANCE & RELIABILITY”...
- BWA 7.00: Optimal settings for Intel Xeon 5570 CPUsSymptom You want to configure optimal settings for Intel Xeon...
- BWA 7.00: Restricted Use of OCFS2Symptom If you observe one or more of the following...
Symptom
You want to find out whether your BWA sizing is correct.
Other terms
BIA, BWA, Accelerator, sizing, overload, Quicksizer, memory consumption, high memory
Reason and Prerequisites
You want to find out whether your BWA sizing is correct.
Solution
The only relevant measure for sizing is the “Disk Size”.
You can find this measure (column “Disk Size [kB]“) in tab “Usage -> Access Statistics” of the TREXAdmintool.
To be within sizing limits, the following statement needs to be true:
“SUM (”Disk Size [kB]“)” is less or equal than “0.5 * < SUM of main memory of all blades>”
Notes:
Backup blades are not taken into account for sizingAny other measure (like “mem. size”) is not reliable for sizing because it may differ during different times of data loads and does not cover worst case scenarios.