| From: | John Naylor <johncnaylorls(at)gmail(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Amit Langote <amitlangote09(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, jian he <jian(dot)universality(at)gmail(dot)com>, Erik Rijkers <er(at)xs4all(dot)nl>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: remaining sql/json patches |
| Date: | 2023-11-28 05:10:18 |
| Message-ID: | CANWCAZaF0a+GCqJN+DP5FwNpDiVt4758Fi-UWn98FunMLaw1EQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Nov 27, 2023 at 8:57 PM Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> Interesting. But inferring a speed effect from such changes is
> difficult. I don't have a good idea about measuring parser speed, but a
> tool to do that would be useful. Amit has made a start on such
> measurements, but it's only a start. I'd prefer to have evidence rather
> than speculation.
Tom shared this test a while back, and that's the one I've used in the
past. The downside for a micro-benchmark like that is that it can
monopolize the CPU cache. Cache misses in real world queries are
likely much more dominant.
https://www.postgresql.org/message-id/14616.1558560331@sss.pgh.pa.us
Aside on the relevance of parser speed: I've seen customers
successfully lower their monthly cloud bills by moving away from
prepared statements, allowing smaller-memory instances.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shubham Khanna | 2023-11-28 05:14:48 | Re: Improve tab completion for ALTER DEFAULT PRIVILEGE and ALTER TABLE |
| Previous Message | Michael Paquier | 2023-11-28 04:22:29 | Re: New instability in stats regression test |