How object pooling works in MTS

Tuesday, July 28, 2009

How object pooling works in MTS.With standard COM, object is released whom client deletes the object or client process terminated, but with MTS (Microsoft Transaction Server), however clients can hold on to the references to objects, but the objects becomes “deactivated” for the period when their services are not required.When client needs the services of an object MTS will try to assign one from its pool of deactivated objects (if available) before resorting to the instantiation of a new object (if name is available).This increases performance of scalability because • Few objects can be shared over many clients, thus reducing the demand over system resources.• Objects can be initialized and waiting “ready to go”, this enables them to react to a request immediately on demand.For example – Database connection is a notoriously expensive operation and in large system can result in unacceptable performance levels.