postgresql - Multiple connection pool on same PostgresSql -
my application has 2 sections mainly,
- user interface written in angular uses django python end.
- heavy map reduce kind of process.
both uses postgres up, doubt if use same connection pool both, @ time when map reduce runnning due heavy lookup other application won't work because of no connection available. there work around this.(avoiding postgres in backlog)
ps: using pgbouncer pooling
simplest approach separating 2 sections. @ least respect connection resources. (whether e.g. memory consumption , gc benefit restructuring not asked for)
you may achieve using 1 of following approaches:
use 2 separate pools, 1 each section.
way, may setup pools according connection requirements per section.change code maintain sufficient "free" resources other section.
quite tedious , useful resource requirements need fine grain control depending on internal state of algorithms.
usually you'd want go suggestion 1.
Comments
Post a Comment