Siebel Server Administration Guide > Application Object Manager Administration > Overview of Siebel Application Object Manager >

Memory Allocation

The Application Object Manager caches information in a couple of different ways. Some information is cached and used by every connection and other information is stored for each user connection.

The Application Object Manager's memory allocation can be broken into three areas:

User Memory

The user area maintains specific information about each user's session. Typically, each user uses 3 MB to 4 MB of memory, though this is dependent on the Siebel application being used. This memory gets released when the task is completed. This may or may not correspond to the end user logging out.

Shared Memory

The next part of memory is for common structures used by every user. This is the largest part of memory for the Application Object Manager. It contains business objects, business components, controls, and other metadata items from the Siebel repository or SRF file. This memory gets loaded on an as needed basis and remains loaded for the life of the process. It is not uncommon for Application Object Manager processes to use more than 150 MB.

Administrative Memory

The third area of memory used by Application Object Manager is to manage the component itself. This memory is relatively small and is used to manage communication between the Application Object Manager and other Siebel Server components. It runs the listener and coordinates threads and tasks.


 Siebel Server Administration Guide, Version 7.5, Rev. C 
 Published: 18 April 2003