| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, PostgreSQL Advocacy Group <pgsql-advocacy(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL 10: Call for Quotes |
| Date: | 2017-08-31 17:34:20 |
| Message-ID: | CA+TgmoYu-_PFzH1GZ7qsdZqU4hvq9NRMey2fuGpRYheB6S7mRg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
On Thu, Aug 31, 2017 at 1:16 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On 31 August 2017 at 17:48, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> I would argue for
>> adding Andres's executor speedups and Amit's hash index work, too
>
> Do we have accepted/verified perf results we can quote?
Andres had a chart showing mammoth speedups on some of the TPC-H
queries which he presented at PGCon. See, e.g. slide 17 at
https://www.pgcon.org/2017/schedule/attachments/462_jit-pgcon-2017-05-25.pdf
I don't know that that's quite formal enough for PR, but it - Q1 in
particular - sure shows a nice gain.
For hash indexes, the benefit is mostly that now they don't go
kablooey after a crash, rather than performance, although there was
performance work done as part of the project too. Not sure what the
best way to showcase this would be.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Clift | 2017-08-31 17:52:04 | Re: PostgreSQL 10: Call for Quotes |
| Previous Message | Simon Riggs | 2017-08-31 17:16:57 | Re: PostgreSQL 10: Call for Quotes |