public inbox for pgsql-performance@postgresql.org
help / color / mirror / Atom feedFrom: Rick Otten <rottenwindfish@gmail.com>
To: Kevin.Hughes@uk.fujitsu.com
Cc: pgsql-performa. <pgsql-performance@postgresql.org>
Subject: Re: Client Server performance & UDS
Date: Sat, 27 May 2017 08:26:31 -0400
Message-ID: <CAMAYy4J1CrDfvTdSpx9zZ-aZ5W=AJmOPKBTRBhg9V69G7B_sjw@mail.gmail.com> (raw)
In-Reply-To: <d9852308baee4c33aa11b4b1d33c8dc3@R01UKEXCASM123.r01.fujitsu.local>
References: <d9852308baee4c33aa11b4b1d33c8dc3@R01UKEXCASM123.r01.fujitsu.local>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
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.Hughes@uk.fujitsu.com" <
Kevin.Hughes@uk.fujitsu.com> wrote:
> 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) so we would expect it to be
> contained in memory. Accesses need to be low latency – unfortunately there
> are “serial” accesses where the result of one access governs the next.
> Luckily the work to be done by the DB is, we believe, very simple and
> hence fast. Everything is running on one (large) server so we use UDS to
> connect the client to the server.
>
>
>
> Out observation (suspicion) is that the latency of the access, as opposed
> to the cost of the query, is high. Having done some investigation we
> believe the UDS latency may be contributing AND the cost imposed by
> postgres in “formatting” the messages between the client and server
> (transformation to network format?).
>
>
>
> We will try and get underneath this with real results/measurements but I
> would appreciate any comments pointers on what we are doing and how/if we
> can optimise this style of applications
>
>
>
>
>
> Cheers
>
>
>
>
>
>
>
>
>
> Unless otherwise stated, this email has been sent from Fujitsu Services
> Limited (registered in England No 96056); Fujitsu EMEA PLC (registered in
> England No 2216100) both with registered offices at: 22 Baker Street,
> London W1U 3BW; PFU (EMEA) Limited, (registered in England No 1578652) and
> Fujitsu Laboratories of Europe Limited (registered in England No. 4153469)
> both with registered offices at: Hayes Park Central, Hayes End Road, Hayes,
> Middlesex, UB4 8FE.
> This email is only for the use of its intended recipient. Its contents are
> subject to a duty of confidence and may be privileged. Fujitsu does not
> guarantee that this email has not been intercepted and amended or that it
> is virus-free.
>
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: rottenwindfish@gmail.com, Kevin.Hughes@uk.fujitsu.com
Subject: Re: Client Server performance & UDS
In-Reply-To: <CAMAYy4J1CrDfvTdSpx9zZ-aZ5W=AJmOPKBTRBhg9V69G7B_sjw@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox