Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qgD89-00Elzi-8E for pgsql-hackers@arkaria.postgresql.org; Tue, 12 Sep 2023 23:49:18 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qgD86-00CdX5-74 for pgsql-hackers@arkaria.postgresql.org; Tue, 12 Sep 2023 23:49:13 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qgD84-00CdWN-5B for pgsql-hackers@lists.postgresql.org; Tue, 12 Sep 2023 23:49:13 +0000 Received: from wout4-smtp.messagingengine.com ([64.147.123.20]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qgD7z-004EbK-CL for pgsql-hackers@postgresql.org; Tue, 12 Sep 2023 23:49:10 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 8446E320093D; Tue, 12 Sep 2023 19:49:04 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Tue, 12 Sep 2023 19:49:05 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= cc:cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm1; t=1694562544; x=1694648944; bh=jF NZ10MnqmFOljIwOKJTl1ryj4PXzD1cUVAqAgmd79c=; b=Iv6U1VMN1fuVgEPGFr UCLmZy+5wRPfptvR5UQF07ma05TdGTznYww6hMHi6R1bb2jPIldHfzzU9KNP1Ir4 7Z6VSONsFnXRO2CF8PQSr3sSrBQUSR7lX96gFx/wMEusFe4dxYW2vtonwmnmi+Rq CrIgE/LdPLEx8/A7f+IrOxq981yjUcCTLitXsWtmJvnDSRsbVjjP/2X28YmVgeHQ 7VnDiKg9pVYDQKNPxnbtZmNtRe4BJlwKkW0WacjiWVY26zRp7QJR2GcwbL7cHceK jjyDol97ZewT8VYfaxmEig+TsiAvnK8oiDRzIacE6N0iy8aupMvrDmB/Yb98izPh IUAQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; t=1694562544; x=1694648944; bh=jFNZ10MnqmFOl jIwOKJTl1ryj4PXzD1cUVAqAgmd79c=; b=RuLjtmmYaEnd/uuuQ/DQ5mOXVedEb WjgLC/eAYueWeCCnrBBNLv4Z2YizzrdF1Iz5cTKXIHhR0j9OzK0wdU1yrQaNrXMZ YLl1ajLVPXWbf8B9sE4X0SPhQddTak1j4Ois6ovFJfjfcbw9RcfuMQtQ4CW50Vzs 23PNK1j7Z4UVClLymeKbUi5y8IFdivom7zJJ9YKj99ObLdZuOwSpzk6fZt+wK1bh TihTPrGxyQqHUAm1hPq+kVnLIek3lh/H62dRpiFCES7EtyZ6fmtBvPCrRLZZd3MM 69WWgF6X7sKvJmhcpWMhm37+skzz+734wERWiA4CbxQs2XNi1rSKB4W/A== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrudeijedgvdejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvfevuffkfhggtggujgesthdtredttddtvdenucfhrhhomheptehnughr vghsucfhrhgvuhhnugcuoegrnhgurhgvshesrghnrghrrgiivghlrdguvgeqnecuggftrf grthhtvghrnhepvdfffeevhfetveffgeeiteefhfdtvdffjeevhfeuteegleduheetvedu ieettddunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomh eprghnughrvghssegrnhgrrhgriigvlhdruggv X-ME-Proxy: Feedback-ID: id4a34324:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 12 Sep 2023 19:49:02 -0400 (EDT) Date: Tue, 12 Sep 2023 16:49:01 -0700 From: Andres Freund To: Daniel Gustafsson Cc: Tom Lane , PostgreSQL Hackers , Thomas Munro , Justin Pryzby , Nazir Bilal Yavuz Subject: Re: Cirrus-ci is lowering free CI cycles - what to do with cfbot, etc? Message-ID: <20230912234901.shdteoa5gk27fb3y@awork3.anarazel.de> References: <20230808021541.7lbzdefvma7qmn3w@awork3.anarazel.de> <20230823065833.vnnfwoi3n2sbw5kf@awork3.anarazel.de> <20230823192239.jxew5s3sjru63lio@awork3.anarazel.de> <3557216.1692824571@sss.pgh.pa.us> <43B6331A-1005-4804-8644-ED30A31839F9@yesql.se> <7BE59586-7390-4906-B5D9-F83681093A8F@yesql.se> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7BE59586-7390-4906-B5D9-F83681093A8F@yesql.se> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, On 2023-08-30 10:57:10 +0200, Daniel Gustafsson wrote: > > On 28 Aug 2023, at 14:32, Daniel Gustafsson wrote: > > > Attached is a patch with a quick PoC for using PQPing instead of using psql for > > connection checks in pg_regress. > > The attached v2 fixes a silly mistake which led to a compiler warning. Still seems like a good idea to me. To see what impact it has, I measured the time running the pg_regress tests that take less than 6s on my machine - I excluded the slower ones (like the main regression tests) because they'd hide any overall difference. ninja && m test --suite setup --no-rebuild && tests=$(m test --no-rebuild --list|grep -E '/regress'|grep -vE '(regress|postgres_fdw|test_integerset|intarray|amcheck|test_decoding)/regress'|cut -d' ' -f 3) && time m test --no-rebuild $tests Time for: master: cassert: real 0m5.265s user 0m8.422s sys 0m8.381s optimized: real 0m4.926s user 0m6.356s sys 0m8.263s my patch (probing every 100ms with psql): cassert: real 0m3.465s user 0m8.827s sys 0m8.579s optimized: real 0m2.932s user 0m6.596s sys 0m8.458s Daniel's (probing every 50ms with PQping()): cassert: real 0m3.347s user 0m8.373s sys 0m8.354s optimized: real 0m2.527s user 0m6.156s sys 0m8.315s My patch increased user/sys time a bit (likely due to a higher number of futile psql forks), but Daniel's doesn't. And it does show a nice overall wall clock time saving. Greetings, Andres Freund