Performance Tuning Guide > Tuning the Siebel Application Object Manager for Performance > Best Practices for AOM Tuning >

Memory Consumers in AOM

In addition to the caches described earlier, this section discusses major memory consumers in AOM components. For more information on some of these topics, see Tuning Customer Configurations for Performance.

• Database client libraries. Database client libraries have their own caches, caching metadata, connections, cursors, and data. Some of these caches can be reduced in size by using Siebel database connection pooling, described in Configuring Database Connection Pooling for AOMs.
• Scripts. A script defined on a business component, applet, or business service is loaded into AOM memory when the script is first invoked.

  For Siebel eScript, garbage collection is performed according to settings that are optimized for each release in order to use server memory and other resources appropriately.

• Heavy configurations. Performance is affected when an application is heavily configured.

Other memory consumers in AOM are the following:

• Navigation pattern. Numerous scenarios that can be used to navigate in the application can make using global caches ineffective.
• Session timeouts. Higher session timeout values mean more active sessions on the server at a time, therefore more memory being used. Lower session timeout values may mean more frequent logins.
• Users per AOM. More users per AOM means more sharing of global resources between the users. While the amount of memory used per user on this AOM is less, more memory is used overall.
• Number of applets on views. More applets configured on views means more business components will be needed at a time, hence higher overall memory usage.
• PDQ size. The list of items in the PDQ (predefined queries) list are maintained on the server for the current business object. The higher the number of items in this list, the more memory it consumes. The size of PDQ strings also determines memory usage.