: Hughes, Kevin
Cc: pgsql-performa.
Subject: Re: [PERFORM] Client Server performance & UDS
Establishing a connection with a PostgreSQL database is a very expensive
process on the database server. On the other hand, establishing a connection
with pgbouncer is very fast.Offloading the connec
On May 30, Rick Otten modulated:
> If your clients are keeping persistent connections open to the
> database, and the latency you are experiencing is within the
> transaction itself, you might look at disk I/O for your WAL (write
> ahead logs) and take a closer look at WAL and checkpoint tuning.
>
3:27
> *To:* Hughes, Kevin
> *Cc:* pgsql-performa.
> *Subject:* Re: [PERFORM] Client Server performance & UDS
>
>
>
> You should have a layer such as pgbouncer between your pg instance and
> your application. It is designed to mitigate the access latency issu
: Rick Otten [mailto:rottenwindf...@gmail.com]
Sent: 27 May 2017 13:27
To: Hughes, Kevin
Cc: pgsql-performa.
Subject: Re: [PERFORM] Client Server performance & UDS
You should have a layer such as pgbouncer between your pg instance and your
application. It is designed to mitigate the access lat
You should have a layer such as pgbouncer between your pg instance and your
application. It is designed to mitigate the access latency issues you
describe.
On May 26, 2017 10:03 AM, "kevin.hug...@uk.fujitsu.com" <
kevin.hug...@uk.fujitsu.com> wrote:
> Hi,
>
>
>
> This is a genera
Hi,
This is a general question around this performance area rather
than a specific performance problem.so I apologise now for a lack of a
specific detail.
We have an application that does many small actions on the DB -
and it's a small DB (a 50/100 Mbytes) s
