Are you seeing this in development or production? I would expect this behavior in development, but never in production. In my experience, connection pools are established and maintained for the run-time of the application. Naturally, if you are deployed in an auto-scaling environment, each instance of your app will get its own pool(s), but that's to be expected.
Walter > On Dec 21, 2017, at 9:11 AM, vaibhav paliwal <[email protected]> > wrote: > > Hi, > > In our rails application we need to establish connection to database based on > the client id in the URL. Currently we are using establish_connection but it > looks like it creates new connection pool each time and executes some queries > to get schema information about DB. Is there a way to cache connection pool ? > I am also curious why did Active Record decided not to cache the connection > pools based on configuration ? I am not sure if its a great idea to subclass > ConnectionHandler and roll my own connection pool caching something like this > any opinions ? > > Thanks > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/rubyonrails-talk/52905ce6-8bc9-422f-becd-ab8609cfc7f2%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/3A748167-EA1F-473B-A0B6-85BCF8748446%40wdstudio.com. For more options, visit https://groups.google.com/d/optout.
