Shared item
1 shares
Performance Considerations for Siebel Development
via Siebel Unleashed by neel on May 04, 2008
A really nice post contributed by a member of Siebel Unleashed forum. This can act a checklist while working on performance related problems. Here is excerpt from the post
Performance Considerations for Siebel Development
In custom configuration and scripting there are areas where performance can be an issue. It is common that these performance issues were not detected during build and unit test because the development environment is usually a smaller data set than system test/UAT environments.
This article will provide Siebel developers with the primary causes of performance problems and a Siebel performance tuning checklist.
Totals displayed in a List Applet
A list applet can be configured to display totals at the bottom of numeric columns. I will not go into detail on how to configure totals for a list applet. Please refer to Siebel Bookshelf for more information on this.
When totals are not configured for a list applet, the resultant query only needs to retrieve the batch of records that should be displayed and then query for a new batch when the user scrolls through the applet. When a list applet is configured to display totals this results in a performance hit as all records must be returned that meet the applet query.
Search Specification on Non-Indexed Columns or Non DB Supported Calculated Fields
The underlying SQL query may be inefficient for a search specification if one or more of the columns used in the search specification are not indexed. The best way to determine this is to perform an explain plan on the resultant query. There are many aspects involved in tuning a SQL query and a DBA should be consulted for help in this area.
To read the complete posts please visit the following thread.
Performance Considerations for Siebel DevelopmentShared by: