Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from ) id 1jHBau-0007Ae-Jq for pgsql-bugs@arkaria.postgresql.org; Wed, 25 Mar 2020 19:21:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1jHBat-0005nP-Ak for pgsql-bugs@arkaria.postgresql.org; Wed, 25 Mar 2020 19:21:39 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1jHBas-0005g5-VW for pgsql-bugs@lists.postgresql.org; Wed, 25 Mar 2020 19:21:39 +0000 Received: from mail-wr1-x443.google.com ([2a00:1450:4864:20::443]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jHBam-00020q-Bj for pgsql-bugs@lists.postgresql.org; Wed, 25 Mar 2020 19:21:37 +0000 Received: by mail-wr1-x443.google.com with SMTP id 65so4750805wrl.1 for ; Wed, 25 Mar 2020 12:21:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=+JTthjk6Mp9eCSHBQrbD8bPfC8n4rh0662rCLeOB8JQ=; b=KCPGHRTnt3GBZfUiHyww1TwS8uXjaw8QqHEDVPJ9dczzGCo2OKip6tpWgINtXzuyo5 ZdFDL70bpi0DExJ/azSygZ6IcKGLL8MqXRIOrqISzjtUSKR5WxtdVlqTB6RD9dTLbK4z 0P71iC6Y2PUXuYiNIpX/DNVM/1DHgutMyZYbRnADTNZe5fFmX3IUzAGUc3TZ3BqCVKTd EgoswtUCYEvA94IhwkPo92c/p7gpFcLMOAoTd6pHVdybCX2bG60vs6emOGMP4cy34e0C CRE6nO9xOMusC61Yu79N5iCdXZW7q/AenKPnTbhSFSlqX6qEuA8Xu9YZY0guvl/h01UK PCag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=+JTthjk6Mp9eCSHBQrbD8bPfC8n4rh0662rCLeOB8JQ=; b=P7OeE7svPKum/0lhhsiCm5Qoko+lErIAFGwHipPo/cDo4DiKKfPuKEoS2r/0f0uqRd 8EZs23W/iojA33voxCppBffezI5XCNWcF8rxDacKPnnNug3PFfNyYtm6w7Dv+GkwMmqb i8sGNd6h4+yzlJISNeyMNewvPQreC8GR04koMp0/w0Vr8+ysHjvTwlmXtP/wULiPrPyM Nj4eQyyffivkiz5iuRXvyX3Prt9YFgaI4dwDB+fX9YI/gcUbfZSg7UzmaGVI16G+6GDY jBqWLky9nBlw7C0k60evg6JVsBBxwHEkcwPIE9SXBK+T7LYJhRnCn2ibh4gllyOwiwOQ EP+Q== X-Gm-Message-State: ANhLgQ31PXY3nUAIqz1gO4iUgvcGYUfSOZO6KTG1rNtrJJvXOBqIof2S T5xgCXrOvS0yl3vCL1FO+B4A1w== X-Google-Smtp-Source: ADFU+vvSjSCozQmD11/IN4PhbIiurJc61Dte+0BLpOHVaUOcFjneDI9gJQrA7PRDOxdrTI8bQaNh2Q== X-Received: by 2002:adf:f1c4:: with SMTP id z4mr5367092wro.342.1585164090877; Wed, 25 Mar 2020 12:21:30 -0700 (PDT) Received: from localhost (ip-86-49-253-141.net.upcbroadband.cz. [86.49.253.141]) by smtp.gmail.com with ESMTPSA id c5sm8639412wma.3.2020.03.25.12.21.29 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 25 Mar 2020 12:21:29 -0700 (PDT) Date: Wed, 25 Mar 2020 20:21:27 +0100 From: Tomas Vondra To: Jeff Janes Cc: rajiv.mca08@gmail.com, pgsql-bugs Subject: Re: BUG #16314: Database Cache Hit Ratio (Warning) Message-ID: <20200325192127.iob4nipkonfcvy7z@development> References: <16314-451e54136ca0556d@postgresql.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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