The project is actually using mod_wsgi (presumably using MPM) - this seems
to explain the rapid increase in the number of connections. It's been
suggested that implementing SQLRelay could be a solution. Is this
sensible? Are there any (better?) alternatives that I could look at?
Cheers,
On 01/06/2016 08:09 AM, Chris Wood wrote:
> The project is actually using mod_wsgi (presumably using MPM) - this
> seems to explain the rapid increase in the number of connections. It's
> been suggested that implementing SQLRelay could be a solution. Is this
> sensible? Are there any (better?)
On Tuesday, 22 December 2015 01:53:59 UTC, Michael Bayer wrote:
>
>
>
> On 12/21/2015 07:44 PM, Chris Wood wrote:
> > Ah, ok - thanks for the explanation - this is different to how I'd been
> > led to believe it worked! However, I know that even when I'm the only
> > person testing the
The sizes for the connection pool are for each instance of your
application. If you have a 10connection pool and you are running 10
instances of your application on the server, you'll easily have 100
connections. If you're running 1 instance that forks, each fork will have
it's own pool (if
Ah, ok - thanks for the explanation - this is different to how I'd been led
to believe it worked! However, I know that even when I'm the only person
testing the application, I'm still getting a large number of connections.
Is there a likely explanation why?
On Monday, 21 December 2015 18:51:25
On 12/21/2015 07:44 PM, Chris Wood wrote:
> Ah, ok - thanks for the explanation - this is different to how I'd been
> led to believe it worked! However, I know that even when I'm the only
> person testing the application, I'm still getting a large number of
> connections. Is there a likely
