Re: POC: Cache data in GetSnapshotData()

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Mithun Cy <mithun(dot)cy(at)enterprisedb(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: POC: Cache data in GetSnapshotData()
Date: 2017-09-21 02:22:00
Message-ID: CA+TgmoYuuhFPifAPHBCFz95hANeMHVoRKtpon0sdAOYTJWiaiQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Sep 20, 2017 at 10:04 PM, Mithun Cy <mithun(dot)cy(at)enterprisedb(dot)com> wrote:
> My current tests show on scylla (2 socket machine with 28 CPU core) I
> do not see any improvement at all as similar to Jesper. But same tests
> on power2 (4 sockets) and Cthulhu(8 socket machine) we can see
> improvements.

OK, makes sense. So for whatever reason, this appears to be something
that will only help users with >2 sockets. But that's not necessarily
a bad thing.

The small regression at 1 client is a bit concerning though.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2017-09-21 02:26:42 Re: Windows warnings from VS 2017
Previous Message Craig Ringer 2017-09-21 02:19:21 Re: Error: dsa_area could not attach to a segment that has been freed