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.89) (envelope-from ) id 1igzAA-0007HO-3D for pgsql-performance@arkaria.postgresql.org; Mon, 16 Dec 2019 22:48:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1igzA8-000301-NL for pgsql-performance@arkaria.postgresql.org; Mon, 16 Dec 2019 22:48:24 +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 1igzA8-0002zt-AL for pgsql-performance@lists.postgresql.org; Mon, 16 Dec 2019 22:48:24 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1igzA5-0006XS-II for pgsql-performance@lists.postgresql.org; Mon, 16 Dec 2019 22:48:23 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id xBGMmGpK028108; Mon, 16 Dec 2019 17:48:16 -0500 From: Tom Lane To: Nicolas Charles cc: pgsql-performance@lists.postgresql.org, Peter Geoghegan , Shijia Wei , Laurenz Albe Subject: Re: Consecutive Query Executions with Increasing Execution Time In-reply-to: References: <19575.1576529417@sss.pgh.pa.us> Comments: In-reply-to Nicolas Charles message dated "Mon, 16 Dec 2019 23:08:52 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <28106.1576536496.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Mon, 16 Dec 2019 17:48:16 -0500 Message-ID: <28107.1576536496@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Nicolas Charles writes: > Could it be that your CPUs is warming and throttling? You didn't mention= the platform used, so I'm not sure whether it's a server or a laptop Hmm, that's an interesting thought. The OP did say the CPU type, but according to Intel's spec page for it [1] the difference between base and turbo frequency is only 4.0 vs 4.2 GHz, which doesn't seem like enough to explain the results ... unless you suppose it actually throttled to below base freq, which surely shouldn't happen that fast. Might be worth watching the CPU frequency while doing the test though. I was speculating about some OS-level problem myself. Plain old "top" might be enough to show relevant info if it's in that area. regards, tom lane [1] https://ark.intel.com/content/www/us/en/ark/products/88195/intel-core-= i7-6700k-processor-8m-cache-up-to-4-20-ghz.html