Investigate setting pgbouncer-web pool to "transaction" mode

RESOLVED WONTFIX

Status

RESOLVED WONTFIX
6 years ago
a year ago

People

(Reporter: jberkus, Unassigned)

Tracking

unspecified
Future
x86
Mac OS X

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
Currently the pgbouncer-web pool ... the one used for the Webapp ... is set to the less efficient "session" mode.  This was probably done for compatibility with some of the older PHP code, and is likely no longer needed.

Today StephenD demonstrated that a relatively low number of fuzzer connections can run PostgreSQL out of connections and shut down the app.  This is partly because of "session" mode.  So being able to switch to the more efficient "transaction" mode would help prevent DOS due to peak usage.  This will become even more true once we move to Django.

This bug is to test transaction mode on stage to make sure that we can safely switch.
Assignee: josh → sdeckelmann
Assignee: sdeckelmann → nobody
I don't think this is relevant anymore. I'm going to close it as WONTFIX. If there's still work to do here, please reopen.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.