The object pool pattern is a software creational design pattern that uses a set of initialised objects kept ready to use, rather than allocating and destroying them on demand. A client of the pool will request an object from the pool and perform operations on the returned object. When the client has finished, it returns the object, which is a specific type of factory object, to the pool rather than destroying it.
Object pooling can offer a significant performance boost in situations where the cost of initializing a class instance is high, the rate of instantiation of a class is high, and the number of instances in use at any one time is low. The pooled object is obtained in predictable time when creation of the new objects (especially over network) may take variable time.
However these benefits are mostly true for objects that are expensive with respect to time, such as database connections, socket connections, threads and large graphic objects like fonts or bitmaps. In certain situations, simple object pooling (that hold no external resources, but only occupy memory) may not be efficient and could decrease performance.
Read more about Object Pool Pattern: Handling of Empty Pools, Pitfalls, Criticism, Examples
Famous quotes containing the words object, pool and/or pattern:
“Pleasure cannot be shared; like Pain, it can only be experienced or inflicted, and when we give pleasure to our Lovers or bestow Charity upon the Needy, we do so, not to gratify the object of our Benevolence, but only ourselves. For the Truth is that we are kind for the same reason as we are cruel, in order that we may enhance the sense of our own Power.”
—Aldous Huxley (1894–1963)
“I hate to say it, Cory, but as a pool player you make a fine speedboat mechanic.”
—Blake Edwards (b. 1922)
“In almost every marriage there is a selfish and an unselfish partner. A pattern is set up and soon becomes inflexible, of one person always making the demands and one person always giving way.”
—Iris Murdoch (b. 1919)