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:
“Art expresses the one, or the same by the different. Thought seeks to know unity in unity; poetry to show it by variety; that is, always by an object or symbol.”
—Ralph Waldo Emerson (18031882)
“I hate to say it, Cory, but as a pool player you make a fine speedboat mechanic.”
—Blake Edwards (b. 1922)
“It was her stern necessity: all things
Are of one pattern made; bird, beast, and flower,
Deceive us, seeming to be many things,
And are but one. Beheld far off, they differ
As God and devil; bring them to the mind,
They dull its edge with their monotony.”
—Ralph Waldo Emerson (18031882)