Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

Size Matters


Properly deploying your SAP BusinessObjects BI4.x  landscape involves more than punching some numbers into a calculator and installing the right number of servers.  Approaching this from a BI systems perspective means understanding how your BI system works and making intelligent decisions to ensure good system performance and stability.

This site contains resources to help you properly size and deploy SAP BusinessObjects BI4 and SAP Lumira in both production and non-production scenarios.  It is important to remember that these resources are not replacements for other existing documentation such as the Installation and Administration Guides where they provide additional information based on generally accepted best practices, internal lab tests, and customer feedback.

These resources are not a replacement for a proper sizing exercise performed by an expert BI consulting architect that can glean the nuances of your particular landscape from discussions with your stakeholders and combine that information with the resources here and his or her own personal learnings.


Sizing and Deployment Resources for SAP BusinessObjects BI 4

Every deployment requires a sizing exercise.  It is critical to fully read and understand the SAP BI 4 Sizing Guide before using Quick Sizer for Sizing SAP BusinessObjects Business Intelligence Suite applications (SMP Login Required). Refer Quick Sizer Tool documentation available on main page for using Classic version.

Sizing and Deployment Resources for SAP Lumira 1.x

Sizing and Deployment Resources for SAP BusinessObjects Design Studio 1.x

Sizing and Deployment Resources for SAP BusinessObjects Lumira 2.0

INFO: SAP QuickSizer calculations for Lumira is now available for use under HANA version of Quick Sizer in conjunction with Sizing guide. 

Sizing and Deployment Resources for SAP BusinessObjects Explorer

Sizing and Deployment Resources for SAP BusinessObjects Mobile

Generic Performance Optimization Tips

Server Optimizations

Apache Split
Reduce back-end load and Improve the User Experience by 'splitting' Web content delivery: Team-up Apache and Tomcat, having them each do what they do best. Apache serves up the static content and does compression natively while Tomcat runs the Web apps. Multiple articles:

Client Optimizations


  • No labels


  1. Hello colleagues,

    In BI Platform Sizing giude there is following information provided for WebIntelligence memory consumption:

    By default, the Web Intelligence Processing server is set to utilize as much memory as it requires and for the clear majority of cases this setting is suitable. However, if either the available memory on the machine is limited, or the documents are particularly large, in terms of data volume and complexity, when the memory usage can be considerable, it may be required to ‘Enable Memory Analysis’.

    In this regard i have a question, how much memory Web Intelligence Processing server can consume if Memory analysis is deactivated. For example we have an instance with 64Gb total and let's say 40 is free after the system start. If we apply excessive load to Webi how much it can consume?

    Thank you very much for clarification.

    With best regards,

  2. Hello Pavel,


         Webi Intelligence Processing server(WIPS) is a C++ based application and by default, has the ability to consume the full capacity of the RAM. Where as in a JAVA based application, the memory consumption is limited by the Xms and Xmx parameters ( i.e. managed by Java memory management).

    However WIPS provides an option to control its memory consumption, by turning ON the ‘Enable Memory Analysis‘ feature.

    Thus in your case, if 40GB is free (out of 64GB) and ‘Enable Memory Analysis‘ turned OFF, then you are making the remaining 40 GB RAM available to be used by "Web Intelligence Processing server". The side effects of this is that, based on the complexity of the Webi reports, there are chances of utilizing the complete available RAM.

    However the ‘Memory Analysis’ is just a mechanism that is called on a regular basis (2mins, then down to 30 seconds depending) and then on the result of the analysis, different things happen within webi that should either reduce the memory usage and/or prevent actions that then lead to more memory being used.

    So, in one way, even with Memory Analysis enabled, its actually possible for the entire memory to be consumed, but in practice that’s so very unlikely indeed.

    Please find the below blog for reference (Some of this advice needs to be updated) i