pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feed From: Tom Lane <tgl@sss.pgh.pa.us>
To: ldh@laurent-hasson.com <ldh@laurent-hasson.com>
Cc: Justin Pryzby <pryzby@telsasoft.com>
Cc: Ranier Vilela <ranier.vf@gmail.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Big Performance drop of Exceptions in UDFs between V11.2 and 13.4
Date: Sun, 22 Aug 2021 15:23:43 -0400
Message-ID: <35729.1629660223@sss.pgh.pa.us> (raw )
In-Reply-To: <MN2PR15MB25601CCA9E337403E1754BDE85C39@MN2PR15MB2560.namprd15.prod.outlook.com >
References: <MN2PR15MB2560AE2A878FBBE88DCFF33385C29@MN2PR15MB2560.namprd15.prod.outlook.com >
<2092859.1629558281@sss.pgh.pa.us >
<MN2PR15MB25607BDC72A325CA9B9D3E3385C29@MN2PR15MB2560.namprd15.prod.outlook.com >
<2136207.1629569846@sss.pgh.pa.us >
<20210821191950.GW10479@telsasoft.com >
<MN2PR15MB2560ED2A8F967B14E7D7881E85C29@MN2PR15MB2560.namprd15.prod.outlook.com >
<20210821221729.GY10479@telsasoft.com >
<MN2PR15MB2560FB03666CEABB651FB32185C29@MN2PR15MB2560.namprd15.prod.outlook.com >
<MN2PR15MB256034533A31A7C11E3C347985C39@MN2PR15MB2560.namprd15.prod.outlook.com >
<CAEudQAocYZieAMgCtXa8Oau8=dVJ1_R1r0coLeF1LfiYkBCTNA@mail.gmail.com >
<20210822154758.GZ10479@telsasoft.com >
<30496.1629654632@sss.pgh.pa.us >
<MN2PR15MB2560C3FF951319B18A3CA83585C39@MN2PR15MB2560.namprd15.prod.outlook.com >
<MN2PR15MB25601CCA9E337403E1754BDE85C39@MN2PR15MB2560.namprd15.prod.outlook.com >
"ldh@laurent-hasson.com" <ldh@laurent-hasson.com> writes:
> So, now, in summary:
> - I have tried V13.4, V12.3, 11.13, 11.2, 11.1 on several Windows VMs and my personal laptop (no VM).
> - All V11.x seem to behave uniformly.
> - Starting with 12.3, I am experiencing the major slowdown in the "with exceptions" scenario.
Interesting. There's no meaningful difference between v11 and v12 as far
as timeout handling goes, so I'm starting to think that that's a red
herring.
(Although, after having done some web-searching, I do wonder why timer.c
is using a manual-reset event. It looks like auto-reset would work
just as well with less code, and I found some suggestions that it might
perform better.)
> So, I was thinking about stuff and a lot of your intuitions seem to drive towards an issue with the compiler used to compile the Winx64 version... But is it possible that the JIT is getting in there and making things weird? Given that it's a major change in V12 and this is when I am starting to see the issue popup, I figured it might be another avenue to look into?
Hm, is JIT even enabled in your build? If so, does setting jit = 0
change anything?
regards, tom lane
view thread (78+ messages) latest in thread
Message-ID: <35729.1629660223@sss.pgh.pa.us>
Permalink: ../35729.1629660223@sss.pgh.pa.us/
Also on: postgresql.org/message-id/35729.1629660223@sss.pgh.pa.us
copy link · copy postgr.es
reply Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, ldh@laurent-hasson.com, pryzby@telsasoft.com, ranier.vf@gmail.com
Subject: Re: Big Performance drop of Exceptions in UDFs between V11.2 and 13.4
In-Reply-To: <35729.1629660223@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox