From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Mathieu Fenniak <mathieu.fenniak@replicon.com>
Cc: pgsql-general@postgresql.org
Subject: Re: Logical decoding CPU-bound w/ large number of tables
Date: Fri, 05 May 2017 21:32:27 -0400
Message-ID: <19256.1494034347@sss.pgh.pa.us> (raw)
In-Reply-To: <20170506012055.hhmx5hirj2yk7d3g@alap3.anarazel.de>
References: <CAHoiPjzea6N0zuCi=+f9v_j94nfsy6y8SU7-=bp4=7qw6_i=Rg@mail.gmail.com>
<20170506012055.hhmx5hirj2yk7d3g@alap3.anarazel.de>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-general>
Andres Freund <andres@anarazel.de> writes:
> On 2017-05-05 14:24:07 -0600, Mathieu Fenniak wrote:
>> It appears that most of the time is spent in the
>> RelfilenodeMapInvalidateCallback and CatalogCacheIdInvalidate cache
>> invalidation callbacks, both of which appear to be invalidating caches
>> based upon the cache value.
> I think optimizing those has some value (and I see Tom is looking at
> that aspect, but the bigger thing would probably be to do fewer lookups.
I'm confused --- the lookup side of things is down in the noise in
Mathieu's trace. Further reducing the number of lookups doesn't seem
like it helps this scenario at all. It might matter once we've whacked
down the cost of invalidations ...
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
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-general@postgresql.org
Cc: tgl@sss.pgh.pa.us, andres@anarazel.de, mathieu.fenniak@replicon.com
Subject: Re: Logical decoding CPU-bound w/ large number of tables
In-Reply-To: <19256.1494034347@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox