Using SAPGUI in WAN

Summary

Symptom

You encounter performance problems when you use SAP GUI in WAN.

Other terms

Front-end resources consumption

Reason and Prerequisites

The performance of the SAP GUI is poor.

Solution

The following actions should improve the performance of the SAPGUI front end:

1. 1. CPU consumption on the front end is reduced significantly when you switch from "New Visual Design" to "Classic Design" according to Note 173028. The corresponding program is stored in "SAPpc/sapgui/". It is particular useful when you use older graphic boards.

1. 2. If there are longer response times due to performance problems in the network (in particular when you are using the SAPGUI in the WAN) you should use the configuration in the SAPLOGON for "Low Speed Connection" (LSC) (see comments). You will find this setting option in saplogon under: SAPLOGON --> PROPERTIES --> ADVANCED. You will find further information on the network load in the SAP Service Marketplace: http://service.sap.com/sizing, Media Center -> Literature.

Remark: "Low Speed Connection" flag
When you switch on the "Low Speed Connection" the dataset sent to the front end is reduced at the expense of the usability: - Menus are no longer completely transferred, but only on request (for instance, if you select a menu option) - As of SAPGUI 4.6D the "Low Speed Connection" function was changed in such a way that screen field names are not transferred either, since this is too resource-intensive in the LSC environment.
Default values (history) and Drag/Relate are deactivated because they require the screen field names.

When you reduce the dataset on the front end, not all the necessary data may be sent to the front end within a roundtrip, which in turn results in an additional roundtrip.
If the performance is mainly determined by latency and not by the bandwidth, in individual cases, this may result in the performance being impaired.