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:
“My object will be, if possible, to form Christian men, for Christian boys I can scarcely hope to make.”
—Thomas Arnold (1795–1842)
“I’ th’ world’s volume
Our Britain seems as of it, but not in’ t;
In a great pool a swan’s nest.”
—William Shakespeare (1564–1616)
“Man is eminently a storyteller. His search for a purpose, a cause, an ideal, a mission and the like is largely a search for a plot and a pattern in the development of his life story—a story that is basically without meaning or pattern.”
—Eric Hoffer (1902–1983)