Re: Connection pool mgmt

[Reggie Burnett]

You are describing a genuine need though I think it should be handled a different way. In your changes that you described earlier, you were releasing connections based on how long they sat idle. This does not accomplish what you are now describing since you are still bound by MinPoolSize. What you are more referring to and what I think we need is a tuning mechanism so the user can learn that his MinPoolSize should be trimmed for optimal working. This will be accomplished in future versions with a "usage advisor" feature. This will be an option that you can turn on and it will log information about how you are inefficiently using the provider.

Example of inefficient usage are selecting more columns than you are actually reading. Many people do a select * when they are only wanting 1 or 2 columns. Another example would be propery trimming the MinPoolSize if the usage advisor sees that a number of the connections are never being used.