Siebel Performance Tuning Guide > Tuning Siebel Web Client > Guidelines for Siebel Web Client Tuning >

Providing Sufficient Web Server and Network Capacity

This topic is part of Guidelines for Siebel Web Client Tuning.

Make sure that your Web server is appropriately configured to meet your performance requirements. See also Specifying Static File Caching.

Make sure that your network capacity (bandwidth) meets your performance requirements, and that your environment supports full duplex Ethernet. For details, review the general requirements for Siebel Enterprise Server installation and configuration, in the Siebel Installation Guide for the operating system you are using.

Several factors impact decisions regarding network bandwidth:

• Application configuration. Large, complex views will require bigger templates, more controls, and more data to be sent from the Web server to the client. If bandwidth is an issue, then it is important to consider user scenarios to determine the optimal size and layout per view.

  For example, for views used frequently, reduce the number of fields displayed. For the high interactive client, the user can decide which columns are required in list applets. Rather than assuming a specific set, let users adjust it as necessary. Provide the minimal number of columns required in the base configuration. For more information, see Tuning Customer Configurations.

• View layout caching. In high interactivity mode, administrators can determine the number of views to be cached locally. If the hardware supports a greater number of views to be cached, then adjust the value accordingly.

  When a view is cached, subsequent visits will require a data update, but the Web templates need not be reloaded. This provides a substantial improvement in overall usability. For more information, see Improving Performance Using View Layout Caching.

• Login. The first login is generally the most expensive operation for the high interactivity client. The client infrastructure caches the main components of the application on first login. Subsequent logins require far fewer resources. Cached objects remain on the client computer until the cache is cleared or a new version of the application configuration is available.