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 1mPmim-0005TH-32 for pgsql-bugs@arkaria.postgresql.org; Mon, 13 Sep 2021 14:14:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mPmil-0008Sc-0K for pgsql-bugs@arkaria.postgresql.org; Mon, 13 Sep 2021 14:14:07 +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 ) id 1mPmik-0008SU-PP for pgsql-bugs@lists.postgresql.org; Mon, 13 Sep 2021 14:14:06 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mPmii-0003vv-D9 for pgsql-bugs@lists.postgresql.org; Mon, 13 Sep 2021 14:14:05 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id A0E7C5C0150; Mon, 13 Sep 2021 10:14:02 -0400 (EDT) Received: from imap21 ([10.202.2.71]) by compute1.internal (MEProxy); Mon, 13 Sep 2021 10:14:02 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eulerto.com; h= mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm2; bh=8Su+cOqa4rOfmmuUrRpOVz6UKc+3FtA 2SCRbQ2tyPWQ=; b=msMGtnG65RbExoknBOe+xY5tzZZ0Hz+vlWrSwkd/zYTJGQL M51a/vFIZ1YLkya+OAWOzv54lUR3Ob4IYOjDypsZNtNKrV5zMugtRD4NK30HZSwe j0jmMRQOjf4Z3qkDZX69Hfx8hHvjxMHgDNTHUP1vyShd01iNpI2XCF8Nb/dc1DT4 IuytTSYk5KRzfd4spo0sc6ZOtl7acCK+kbvhsKfil5PCRzbeE9nJ9/DpkrwJ/jWc RA0KJ86RuRg6FmE+ySWxmefo6+eBXCZtgpyScwBbSHOBy2VKAxj1+wLhszljoeys Qr3lKs8wCMMmMX+n0YFZb6Vm81tLnzkG/UnGtNg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=8Su+cO qa4rOfmmuUrRpOVz6UKc+3FtA2SCRbQ2tyPWQ=; b=t66mBlpFI/aoYtOibqlPSi 5nFPErzEr2mgehKzV77kmVW/W+2xPa2fExIVeyUiThEQXFtFUHx39jPqzK05+xO5 dRRNCVVG+l0HGGlUHPXbuRhTckdGL5S5XMNuQzHKMLpTD9MTVP3NK5rMLo8rCacg 3hHprqBxok5PH4KZSJaTNNeoJ8sUnzYPVSrJxhnLtbU1AoYckLUX8zszyI4WfSfB BR9msJdtRzE+r6wFDi9hgOrIkCrJE63OgfMTLD4EDdOy8plgz/q64p3hmUAWdrhw QfRo7YU2OjpvBG0/1gDUA2Flrq40S3DtDVPjCGVyPmOV24a5ggtTz7nYp9BUr6wg == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrudegjedgjedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesrgdtreerreertdenucfhrhhomhepfdfguhhl vghrucfvrghvvghirhgrfdcuoegvuhhlvghrsegvuhhlvghrthhordgtohhmqeenucggtf frrghtthgvrhhnpedthedvtdefledtfedtieduieekfedtleekveduveevteehtdeigfek leekveelkeenucffohhmrghinhepphhgtghonhdrohhrghdpphhoshhtghhrvghsqhhlrd horhhgpdgvnhhtvghrphhrihhsvggusgdrtghomhenucevlhhushhtvghrufhiiigvpedt necurfgrrhgrmhepmhgrihhlfhhrohhmpegvuhhlvghrsegvuhhlvghrthhordgtohhm X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id B7A6B51C0061; Mon, 13 Sep 2021 10:14:01 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.5.0-alpha0-1229-g7ca81dfce5-fm-20210908.005-g7ca81dfc Mime-Version: 1.0 Message-Id: <66a182fa-6ae3-4eab-9137-a8ec9dbaf747@www.fastmail.com> In-Reply-To: References: <17185-0a073d43312fee34@postgresql.org> Date: Mon, 13 Sep 2021 11:13:41 -0300 From: "Euler Taveira" To: "arjun shetty" , "pgsql-bugs@lists.postgresql.org" Subject: Re: BUG #17185: PostgreSQL performance GNU vs LLVM Content-Type: multipart/alternative; boundary=679495de8a1d43109970ec3561039e5d List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --679495de8a1d43109970ec3561039e5d Content-Type: text/plain On Mon, Sep 13, 2021, at 10:59 AM, arjun shetty wrote: > Hi All > I would like to know any comments or inputs #17185 > I understand the benefits of using JIT - TPC-H from the link: https://www.pgcon.org/2017/schedule/attachments/467_PGCon%202017-05-26%2015-00%20ISPRAS%20Dynamic%20Compilation%20of%20SQL%20Queries%20in%20PostgreSQL%20Using%20LLVM%20JIT.pdf > I would like to know TPC-C performance GCC vs Clang(llvm).(# reference the below mail) This mailing list is used to report bugs. Since this is *not* a bug, I recommend that you ask these questions on -performance or -hackers. https://www.postgresql.org/list/ -- Euler Taveira EDB https://www.enterprisedb.com/ --679495de8a1d43109970ec3561039e5d Content-Type: text/html Content-Transfer-Encoding: quoted-printable
On Mon, Sep 13,= 2021, at 10:59 AM, arjun shetty wrote:
Hi All
I would like to know a= ny comments or inputs #17185
I would like= to know TPC-C performance GCC vs Clang(llvm).(# reference the below mai= l)
This mailing list is used to report bugs. = Since this is *not* a bug, I
recommend that you ask these = questions on -performance or -hackers.



--
Euler Taveir= a
EDB   https://www.enterprisedb.com/
<= div>
--679495de8a1d43109970ec3561039e5d--