The sizing model is based on the following preconditions:
1 We only consider “direct communication”. Possible local proxy servers tunneling messages to and from the Integration Servers are not considered.
2 We assume that data is persisted twice, once for each of two asynchronous steps (the data is initially persisted after it is received and then again after processing). If data is persisted more than twice (for example, for debugging purposes), more disk space will be required.
3 The measurements are calculated against an average CPU consumption of 70% (see the general sizing procedure at SAP1).
4 The sizing guidelines do not include additional requirements caused by data archiving, data deletion or reorganization.
5 Sizing is for SAP Web Application Server 6.40.
6 Processing by the Adapter Framework is taken into account.
please view the sizing XI 3.0 PDF doc
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/72e2bb90-0301-0010-e883-c390ad8a...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.