A server might provide, a single instance container, at most, for a conglomeration at any given time, or it might have the capability to provide multiple instance containers. Enabling a conglomeration to support multiple concurrent instance containers is known as container pooling. A typical use of container pooling is to increase scalability when contention for system resources within a single instance container is a limiting factor.
For historical reasons, parts of COMT are designed around the assumption that there is a one-to-one correspondence between conglomerations and instance containers and, therefore, the tracker cannot enable information about individual instance containers to be exchanged in cases where container pooling is in use.
Instance pooling refers to enabling component instances that are no longer active to return to a pool for reuse. A typical use of instance pooling is to reduce the performance penalty for the creation and destruction of short-lived component instances. A COMT server that enables instance pooling might track pooling behavior and expose separate statistics for pooled and active component instances.