| From: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
|---|---|
| To: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
| Cc: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Maxim Orlov <orlovmg(at)gmail(dot)com>, Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Custom tuplesorts for extensions |
| Date: | 2022-07-21 03:44:26 |
| Message-ID: | CAFBsxsGQ-OkE8G8akdF3pvE1ZkAq5c8f5zyvQ0JBPXOt0k3UGQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jul 12, 2022 at 3:23 PM Alexander Korotkov <aekorotkov(at)gmail(dot)com>
wrote:
> There are some places, which potentially could cause a slowdown. I'm
> going to make some experiments with that.
I haven't looked at the patches, so I don't know of a specific place to
look for a slowdown, but I thought it might help to perform the same query
tests as my most recent test for evaluating qsort variants (some
description in [1]), and here is the spreadsheet. Overall, the differences
look like noise. A few cases with unabbreviatable text look a bit faster
with the patch. I'm not sure if that's a real difference, but in any case I
don't see a slowdown anywhere.
[1]
https://www.postgresql.org/message-id/CAFBsxsHeTACMP1JVQ%2Bm35-v2NkmEqsJMHLhEfWk4sTB5aw_jkQ%40mail.gmail.com
--
John Naylor
EDB: http://www.enterprisedb.com
| Attachment | Content-Type | Size |
|---|---|---|
| master-vs-custom-ext-v2.ods | application/vnd.oasis.opendocument.spreadsheet | 35.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amul Sul | 2022-07-21 04:08:17 | Re: GetStandbyFlushRecPtr() : OUT param is not optional like elsewhere. |
| Previous Message | John Naylor | 2022-07-21 03:20:30 | Re: i.e. and e.g. |