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:
“Our object in the construction of the state is the greatest happiness of the whole, and not that of any one class.”
—Plato (c. 427–347 B.C.)
“I hate to say it, Cory, but as a pool player you make a fine speedboat mechanic.”
—Blake Edwards (b. 1922)
“Every child has an inner timetable for growth—a pattern unique to him. . . . Growth is not steady, forward, upward progression. It is instead a switchback trail; three steps forward, two back, one around the bushes, and a few simply standing, before another forward leap.”
—Dorothy Corkville Briggs (20th century)