Subject Re: Caching retention using a persistent dummy database connection?
Author jeff_j_dunlap
--- In, "Adam" <s3057043@...> wrote:
> What about a connection pool? You can establish n* connections and
> manage them through your pool. When a query needs to be run, simply
> grab an active connection out of the pool. If you run out, create
> at that time.
> Holding the connections open reduces the overheads associated with
> establishing the connection / authentication etc and should keep the
> database interesting to the server.
> I would be very surprised if an active *connection* had anything to
> with garbage collection. A long running active *transaction* *is*
> issue.
> Adam
> * n connections is a number that is based on your expected load. It
> must be high enough that you are covered 99% of the time, but not
> high that it wastes your server resources for no noticeable benefit.

Thanks for the good suggestion.