0

Recently I started researching more information about the object pool design pattern and I ran into questions that I couldn't found them an answer.

the idea of the object pool pattern is to save expensive resources by reusing them. for examle the connection to the db is a very expensive resource. Therefore i would like to add it to the "pool".

I have always been taught to keep the connection open as little as possible. I may get this all wrong, but in my point of view, creating a new connection and keeping it alive for a long period of time (in the pool) its just a waste of resources. The connection may not be created several times, but it will alway be open.

I would glad to have an explanation.

Shir
  • 1
  • 1
  • Isn't it obvious, that you can close the pooled resources, if they are not used for an arbitrary amount of time? Noone says, that you have to keep them alive forever, instead find an optimal tradeoff between resource costs over time / costs for object creation. – SME_Dev Feb 06 '15 at 14:56

1 Answers1

1

On the one hand creating new connection may be bad due to long creation time

Other extreme which is full reuse may also be problematic since you are holding resources for long time.

Object pool pattern allows you to configure this and (for example) timeout connection after some time. As every performance-oriented solution it requires some tuning to specific case. This pattern is a place where you should keep this configuration.

Marcin Szymczak
  • 11,199
  • 5
  • 55
  • 63