From: Tomas Vondra <tomas.vondra@2ndquadrant.com>
To: tsunakawa.takay@fujitsu.com <tsunakawa.takay@fujitsu.com>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: SLRU statistics
Date: Mon, 20 Jan 2020 17:37:54 +0100
Message-ID: <20200120163754.mbbkbhzaummlo47c@development> (raw)
In-Reply-To: <OSAPR01MB5073426AFE2F2A524948FA6CFE320@OSAPR01MB5073.jpnprd01.prod.outlook.com>
References: <20200119143707.gyinppnigokesjok@development>
<OSAPR01MB5073426AFE2F2A524948FA6CFE320@OSAPR01MB5073.jpnprd01.prod.outlook.com>
On Mon, Jan 20, 2020 at 01:04:33AM +0000, tsunakawa.takay@fujitsu.com wrote:
>From: Tomas Vondra <tomas.vondra@2ndquadrant.com>
>> One of the stats I occasionally wanted to know are stats for the SLRU
>> stats (we have couple of those - clog, subtrans, ...). So here is a WIP
>> version of a patch adding that.
>
>How can users take advantage of this information? I think we also need
>the ability to set the size of SLRU buffers. (I want to be freed from
>the concern about the buffer shortage by setting the buffer size to its
>maximum. For example, CLOG would be only 1 GB.)
>
You're right the users can't really take advantage of this - my primary
motivation was providing a feedback for devs, benchmarking etc. That
might have been done with DEBUG messages or something, but this seems
more convenient.
I think it's unclear how desirable / necessary it is to allow users to
tweak those caches. I don't think we should have a GUC for everything,
but maybe there's some sort of heuristics to determine the size. The
assumption is we actually find practical workloads where the size of
these SLRUs is a performance issue.
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
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: tomas.vondra@2ndquadrant.com, tsunakawa.takay@fujitsu.com
Subject: Re: SLRU statistics
In-Reply-To: <20200120163754.mbbkbhzaummlo47c@development>
* 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