| From: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
|---|---|
| To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
| Cc: | Ronan Dunklau <ronan(dot)dunklau(at)aiven(dot)io>, James Coleman <jtc331(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>, Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
| Subject: | Re: [PATCH] Use optimized single-datum tuplesort in ExecSort |
| Date: | 2021-07-14 23:30:26 |
| Message-ID: | CAFBsxsEegvJsvUUL-rr7=-gE92=ku5w7FQHK6694VRNFt=SSwQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jul 14, 2021 at 6:14 AM David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
> It would be good to get a 2nd opinion about this idea. Also, more
> benchmark results with v6 and v8 would be good too.
I tested this on an older Xeon, gcc 8.4 (here median of each test, full
results attached):
test HEAD v6 v8
Test1 588 1007 998
Test2 198 202 197
Test3 374 516 512
Test4 172 165 166
Test5 255 279 283
Test6 227 251 251
Test7 145 147 146
Test8 474 783 770
Test4 could be a regression, but 2 and 7 look fine here.
--
John Naylor
EDB: http://www.enterprisedb.com
| Attachment | Content-Type | Size |
|---|---|---|
| datum-sort-test-JCN-1.txt | text/plain | 3.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2021-07-14 23:43:20 | Re: [PATCH] Use optimized single-datum tuplesort in ExecSort |
| Previous Message | Tom Lane | 2021-07-14 23:29:04 | Re: Add missing function abs (interval) |