The best approach is to analyze each upgrade individually and add the resulting requirements. More information about additional resources to add when upgrading from one release to the next is available in this SAP note.
Procedure:
Monitor CPU utilization, table growth, and memory use:
CPU and memory utilization: OS Monitor, transaction ST06
Frontend network load: statistical data records, transaction ST03N
Set these in relation to a meaningful business figure, such as number of concurrent users or number of active projects
Add the additional load to the existing load Note that there are two types of upgrade: technical and functional.A technical upgrade is an upgrade from one release to the next higher release of a particular SAP solution (e.g. SAP R/3 Enterprise à SAP ECC 6.0). In this case, significant differences with regard to architecture and functionalities are not expected (performance will not change significantly).Since sizings using the Quick Sizer are based on specific scenarios and contain many assumptions, the Quick Sizer is not the appropriate tool to size technical upgrades. It is much more accurate to measure the current resource requirements of the system and adding the requirements of the new release. SAP provides upgrade notes with information about additional resources for CPU, memory, and disk when upgrading from one release to another.
Judge whether your current hardware is sufficient or additional hardware is required.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.