pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Shawn Debnath <sdn@amazon.com>
To: Andrey Borodin <x4mmm@yandex-team.ru>
Cc: Julien Rouhaud <rjuju123@gmail.com>
Cc: Gilles Darold <gilles@darold.net>
Cc: Tomas Vondra <tomas.vondra@enterprisedb.com>
Cc: Tomas Vondra <tomas.vondra@2ndquadrant.com>
Cc: Alexander Korotkov <aekorotkov@gmail.com>
Cc: Anastasia Lubennikova <a.lubennikova@postgrespro.ru>
Cc: Daniel Gustafsson <daniel@yesql.se>
Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Cc: Thomas Munro <thomas.munro@gmail.com>
Subject: Re: MultiXact\SLRU buffers configuration
Date: Thu, 20 Jan 2022 16:19:49 -0800
Message-ID: <Yen8JWdm4u33J58Y@f01898859afd.ant.amazon.com> (raw)
In-Reply-To: <990B810E-8944-4749-A820-4F46A8CB8502@yandex-team.ru>
References: <CA+hUKGLCLDtgDj2Xsf0uBk5WXDCeHxBDDJPsyY7m65Fde-=pyg@mail.gmail.com>
	<B8FACD14-E3AB-4EB3-8CCC-E93697C54F72@yandex-team.ru>
	<CA+hUKGKzPSXYowH=Y8NiuUD8gdyD225-WHaEzXT1E0Sa8RopVQ@mail.gmail.com>
	<494C5E7F-E410-48FA-A93E-F7723D859561@yandex-team.ru>
	<28051640513399@vla1-36b7415cbc1b.qloud-c.yandex.net>
	<20220114092838.gbr6ea7zxbaespsr@jrouhaud>
	<YeH3FU0ypOA+Kdf8@f01898859afd.ant.amazon.com>
	<A66F1597-EC9E-44F2-B1A1-4377016A5053@yandex-team.ru>
	<YemDdpMrsoJFQJnU@f01898859afd.ant.amazon.com>
	<990B810E-8944-4749-A820-4F46A8CB8502@yandex-team.ru>

On Thu, Jan 20, 2022 at 09:21:24PM +0500, Andrey Borodin wrote:
> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
>
> > 20 янв. 2022 г., в 20:44, Shawn Debnath <sdn@amazon.com> написал(а):
> Can you please also test 2nd patch against a large multixact SLRUs?
> 2nd patch is not intended to do make thing better on default buffer sizes. It must save the perfromance in case of really huge SLRU buffers.

Test was performed on 128/256 for multixact offset/members cache as 
stated in my previous email.  Sure I can test it for higher values - but 
what's a real world value that would make sense? We have been using this 
configuration successfully for a few of our customers that ran into 
MultiXact contention.

-- 
Shawn Debnath
Amazon Web Services (AWS)





view thread (123+ messages)  latest in thread

Message-ID: <Yen8JWdm4u33J58Y@f01898859afd.ant.amazon.com>
Permalink:  ../Yen8JWdm4u33J58Y@f01898859afd.ant.amazon.com/
Also on:    postgresql.org/message-id/Yen8JWdm4u33J58Y@f01898859afd.ant.amazon.com

 · 

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-hackers@postgresql.org
  Cc: sdn@amazon.com, x4mmm@yandex-team.ru, rjuju123@gmail.com, gilles@darold.net, tomas.vondra@enterprisedb.com, tomas.vondra@2ndquadrant.com, aekorotkov@gmail.com, a.lubennikova@postgrespro.ru, daniel@yesql.se, horikyota.ntt@gmail.com, thomas.munro@gmail.com
  Subject: Re: MultiXact\SLRU buffers configuration
  In-Reply-To: <Yen8JWdm4u33J58Y@f01898859afd.ant.amazon.com>

* 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