Siebel 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.
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.