Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-performance-owner+archive@lists.postgresql.org>)
	id 1nZvdy-0000T7-5s
	for pgsql-performance@arkaria.postgresql.org; Thu, 31 Mar 2022 14:19:22 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-performance-owner+archive@lists.postgresql.org>)
	id 1nZvdw-0003v6-QN
	for pgsql-performance@arkaria.postgresql.org; Thu, 31 Mar 2022 14:19:20 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <gc@mnc.ch>)
	id 1nZvdw-0003uw-GZ
	for pgsql-performance@lists.postgresql.org; Thu, 31 Mar 2022 14:19:20 +0000
Received: from mail.mnc.ch ([62.2.77.205])
	by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <gc@mnc.ch>)
	id 1nZvdt-0003pC-NR
	for pgsql-performance@lists.postgresql.org; Thu, 31 Mar 2022 14:19:19 +0000
X-Virus-Scanned: amavisd-new at mnc.ch
Sender: gc@mnc.ch
Received: by gc-P7xxDM3-G.localdomain (Postfix, from userid 1000)
	id 4762389374; Thu, 31 Mar 2022 16:18:37 +0200 (CEST)
From: Guillaume Cottenceau <gc@mnc.ch>
To: pgsql-performance@lists.postgresql.org
Subject: Re: Postgresql TPS Bottleneck
References: 
 <VI1PR04MB31338E811E0896D00D85B69B97E19@VI1PR04MB3133.eurprd04.prod.outlook.com>
Date: Thu, 31 Mar 2022 16:18:37 +0200
In-Reply-To: 
 <VI1PR04MB31338E811E0896D00D85B69B97E19@VI1PR04MB3133.eurprd04.prod.outlook.com>
	(wakandavision@outlook.com's message of "Thu, 31 Mar 2022 11:50:34
	+0000")
Message-ID: <87zgl64342.fsf@mnc.ch>
MIME-Version: 1.0
Content-Type: text/plain
List-Id: <pgsql-performance.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-performance@lists.postgresql.org>
List-Owner: <mailto:pgsql-performance-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-performance>
Archived-At: <https://www.postgresql.org/message-id/87zgl64342.fsf%40mnc.ch>
Precedence: bulk

<wakandavision 'at' outlook.com> writes:

> Optimally I would like to fully use the CPU and get about 3-4 times
> more TPS (if even possible).

Disclaimer: I'm really not a pg performance expert.
I don't understand your hope to fully use the CPU; if your
scenario is disk-limited, which may very well be the case, then
of course you cannot fully use the CPU. With synchronous commits
and fsync, the system is probably spending time just waiting for
the disks to report the writes completion. Are iostat/vmstat
showing a lot of IO-wait?
Also, if you can live with a few lost transactions in case of
server crash, synchronous_commit=off is very ok and provides a
lot of performance gain.

-- 
Guillaume Cottenceau