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

Testing Performance for Web Clients

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

Oracle Advanced Customer Services offers general guidance based on information known about the characteristics of the configured Siebel application. Contact your Oracle sales representative to request assistance from Oracle Advanced Customer Services.

Customer testing is advised in any case, because assumptions are based on general data. Actual experience can vary due to use-case scenarios. Select a few of the most common scenarios: those that represent the highest percentage of activity. Collect the overall bandwidth used.

Make sure that you are testing with warm views (already visited and cached) if this is how the application will be used most of the time, assuming that users log in and use the application for four to eight hours at a time before logging off and starting a new session later.

When you estimate bandwidth required for several users sharing a low-bandwidth connection, consider use-cases carefully and plan accordingly. Rather than planning for worst-case network-performance scenarios (such as all users simultaneous pressing the Enter key or visiting a new view), it is likely that very few users are actually using the network at the same time. For more information about performance monitoring, see Monitoring Siebel Application Performance with Siebel ARM.

Web client performance also depends on browser performance. For general information about this issue for Siebel Open UI, see Deploying Siebel Open UI.