| From: | Yuya Watari <watari(dot)yuya(at)gmail(dot)com> |
|---|---|
| To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Making empty Bitmapsets always be NULL |
| Date: | 2023-06-22 08:59:13 |
| Message-ID: | CAJ2pMkY+i1Vk_3gST06jiO+8ZvYTzMTskVX+wDoG7WnkGvpchQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello,
On Tue, Jun 20, 2023 at 1:17 PM David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
> I've adjusted the attached patch to do that.
Thank you for updating the patch. The v4 patch looks good to me.
I ran another experiment. In the experiment, I issued queries of the
Join Order Benchmark [1] and measured its planning times. The
following table shows the result. The v4 patch obtained outstanding
performance improvements in planning time. This result supports the
effectiveness of the patch in real workloads.
Table 1: Planning time and its speedup of Join Order Benchmark
(n: the number of partitions of each table)
(Speedup: higher is better)
--------------------
n | Speedup (v4)
--------------------
2 | 102.4%
4 | 101.0%
8 | 101.6%
16 | 103.1%
32 | 107.5%
64 | 115.7%
128 | 142.9%
256 | 187.7%
--------------------
[1] https://github.com/winkyao/join-order-benchmark
--
Best regards,
Yuya Watari
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2023-06-22 09:07:42 | Re: Skip collecting decoded changes of already-aborted transactions |
| Previous Message | Yuya Watari | 2023-06-22 08:49:34 | Re: Making empty Bitmapsets always be NULL |