Is there any reason for an object pool to not be treated as a singleton?

Posted by Chris Charabaruk on Stack Overflow See other posts from Stack Overflow or by Chris Charabaruk
Published on 2011-02-09T19:24:23Z Indexed on 2011/02/13 15:25 UTC
Read the original article Hit count: 320

I don't necessarily mean implemented using the singleton pattern, but rather, only having and using one instance of a pool. I don't like the idea of having just one pool (or one per pooled type). However, I can't really come up with any concrete situations where there's an advantage to multiple pools for mutable types, at least not any where a single pool can function just as well.

What advantages are there to having multiple pools over a singleton pool?

© Stack Overflow or respective owner

Related posts about design-patterns

Related posts about architecture