pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tomas Vondra <tomas.vondra@2ndquadrant.com>
To: Jeff Janes <jeff.janes@gmail.com>
Cc: rajiv.mca08@gmail.com, pgsql-bugs <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #16314: Database Cache Hit Ratio (Warning)
Date: Wed, 25 Mar 2020 20:21:27 +0100
Message-ID: <20200325192127.iob4nipkonfcvy7z@development> (raw)
In-Reply-To: <CAMkU=1yVoNOHZ2pwTo7H0VL9Yc1fi81ik9EEk_SzEW+kwp+TsQ@mail.gmail.com>
References: <16314-451e54136ca0556d@postgresql.org>
	<CAMkU=1yVoNOHZ2pwTo7H0VL9Yc1fi81ik9EEk_SzEW+kwp+TsQ@mail.gmail.com>

On Tue, Mar 24, 2020 at 11:44:10AM -0400, Jeff Janes wrote:
>On Tue, Mar 24, 2020 at 8:06 AM PG Bug reporting form <
>noreply@postgresql.org> wrote:
>
>> The following bug has been logged on the website:
>>
>> Bug reference:      16314
>> Logged by:          Rajiv Ranjan
>> Email address:      rajiv.mca08@gmail.com
>> PostgreSQL version: 9.6.0
>> Operating system:   Red Hat Enterprise Linux Server release 7.6 (Maip)
>> Description:
>>
>> Hi,
>>
>> Currently, we are receiving a warning "Database Cache Hit Ratio
>> (%)(Warning)" from one of the monitoring tools.
>>
>
>This is not a bug in PostgreSQL.  It is arguably a bug in your unnamed
>monitoring tool.
>

Yeah, not a PostgreSQL bug.

>It is a dumb warning. The disk is there to be read from--doing so is not
>inherently a problem. Ignore the warning or disable it.
>

I wouldn't say it's entirely dumb, improving cache hit ratio may make 
huge difference, but it requires a lot more information than was
provided.

Rajiv, please send your question to pgsql-general or pgsql-performance
list, and be sure to include information about the system (amount of RAM
for example), resource utilization, workload, threshold currently used
by the alert, actual cache hit ratio, etc.

>Are the queries you care about too slow because data is occasionally read
>from disk?
>

Yeah, it makes little sense to deal with this unless you can demonstrate
some practical impact. In my experience low cache hit ratio values are
an issue with write-intensive workloads, in which case it may cause
significant write amplification.


regards

-- 
Tomas Vondra                  http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services





view thread (6+ messages)  latest in thread

Message-ID: <20200325192127.iob4nipkonfcvy7z@development>
Permalink:  ../20200325192127.iob4nipkonfcvy7z@development/
Also on:    postgresql.org/message-id/20200325192127.iob4nipkonfcvy7z@development

 · 

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-bugs@postgresql.org
  Cc: tomas.vondra@2ndquadrant.com, jeff.janes@gmail.com, pgsql-bugs@lists.postgresql.org
  Subject: Re: BUG #16314: Database Cache Hit Ratio (Warning)
  In-Reply-To: <20200325192127.iob4nipkonfcvy7z@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