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:
“If the heart beguiles itself in its choice [of a wife], and imagination will give excellencies which are not the portion of flesh and blood:Mwhen the dream is over, and we awake in the morning, it matters little whether ‘tis Rachael or Leah,—be the object what it will, as it must be on the earthly side ... of perfection,—it will fall short of the work of fancy, whose existence is in the clouds.”
—Laurence Sterne (1713–1768)
“I caught a blackjack right behind my ear. A black pool opened up at my feet. I dived in. It had no bottom. I felt pretty good—like an amputated leg.”
—John Paxton (1911–1985)
“His talent was as natural as the pattern that was made by the dust on a butterfly’s wings. At one time he understood it no more than the butterfly did and he did not know when it was brushed or marred. Later he became conscious of his damaged wings and of their construction and he learned to think and could not fly any more because the love of flight was gone and he could only remember when it had been effortless.”
—Ernest Hemingway (1899–1961)