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 ) id 1m1XmT-00011H-HS for pgsql-hackers@arkaria.postgresql.org; Thu, 08 Jul 2021 17:25:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1m1XmR-0002eM-MQ for pgsql-hackers@arkaria.postgresql.org; Thu, 08 Jul 2021 17:25:43 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m1XmR-0002da-Eh for pgsql-hackers@lists.postgresql.org; Thu, 08 Jul 2021 17:25:43 +0000 Received: from sfr-1.cri.mines-paristech.fr ([77.158.180.225] helo=smtp.cri.ensmp.fr) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m1XmO-0008Um-ET for pgsql-hackers@postgresql.org; Thu, 08 Jul 2021 17:25:42 +0000 Received: from pseudo (185.141.6.84.rev.sfr.net [84.6.141.185]) by smtp.cri.ensmp.fr (Postfix) with ESMTPSA id 446E8C017B; Thu, 8 Jul 2021 19:27:40 +0200 (CEST) Date: Thu, 8 Jul 2021 19:25:38 +0200 (CEST) From: Fabien COELHO X-X-Sender: fabien@pseudo To: Hannu Krosing cc: Kyotaro Horiguchi , nagata@sraoss.co.jp, gregsmithpgsql@gmail.com, pgsql-hackers , david.christensen@crunchydata.com Subject: Re: pgbench logging broken by time logic changes In-Reply-To: Message-ID: References: <20210617025138.04a35c3ae9a6cd40c077cea0@sraoss.co.jp> <20210617122342.74aa8e65b186a7f2e0034533@sraoss.co.jp> <20210617.141756.654908256727895408.horikyota.ntt@gmail.com> User-Agent: Alpine 2.22 (DEB 394 2020-01-19) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="2056645051-1255961880-1625765139=:233209" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --2056645051-1255961880-1625765139=:233209 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8BIT Hello Hannu, >> I'm not sure we have transaction lasts for very short time that >> nanoseconds matters. > > Nanoseconds may not matter yet, but they could be handy when for > example we want to determine the order of parallel query executions. > > We are less than an order of magnitude away from being able to do 1M > inserts/updates/deletes per second, so microseconds already are not > always 100% reliable. ISTM that 1M tps would be with really a lot of parallel clients, thus the latency of each would be quite measurable, so that µs would still make sense for measuring their performance? If an actual network is involved, the network latency is already 100-200 µs even before executing any code. -- Fabien. --2056645051-1255961880-1625765139=:233209--