First, define your performance baseline using actual business requirements, and involve both the implementation and technical teams when setting up this baseline.Second, when dealing with your custom code, remember that you can often boost system performance by allowing your teams sufficient time to analyze and optimize that coding.Since latency cannot be tuned, one solution to dealing with it is to simply try to keep the network traffic, especially synchronous communication, as low as possible.Consolidating onto one server means that more user-driven load and background-driven load will need to be processed, especially because these loads may be running in parallel (as there is no longer a clear distinction between day and night)., which encompasses all software pieces in one server or one database.This consolidation, which I'll call "going global" (see Figure 1), promises standardized processes across languages and countries, financial gains through easier maintenance, streamlined data management, and simplified reporting — among other benefits.Because of the increased load, check your custom applications for: * For more information, see "SAP's Strategy for End-to-End ILM Success: The Information Lifecycle Management Solution from SAP Bridges the Gap Between Applications and Storage Technology for Legal Compliance," a Performance & Data Management Corner column by Dr.Axel Herbst and Tanja Kaufmann in the January-March 2008 issue of I'd like to leave you with three pieces of advice for evaluating — and improving — system performance, especially if you're considering consolidating on a single global instance.
She also supports the SAP field in feasibility studies.
During the monitored week: In the following sections, I will provide an overview of the typical performance metrics within each architectural layer of SAP software.
I will also offer some hints about which potential bottlenecks to safeguard and where to emphasize the performance optimization of custom coding.
If more users are accessing the central system through a wide area network, consider the following aspects: Latency is the minimum amount of time a network packet needs to go from location A to location B, bypassing several gateways and routers along the way.
Particularly when moving to a single global instance, latency is one performance factor that must not be underestimated.
And third, devise an efficient housekeeping policy whereby you create rules to limit data growth. *For more information, please see "Speed Up High-Throughput Business Transactions with Parallel Processing — No Programming Required!