| From: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: test_json_parser/002_inline is kind of slow |
| Date: | 2025-09-27 00:06:43 |
| Message-ID: | CAOYmi+==2G8SYddQz09+=QjaxeBF1fVTpYUc3S-HJzhjQRkxZw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Sep 26, 2025 at 9:26 AM Jacob Champion
<jacob(dot)champion(at)enterprisedb(dot)com> wrote:
> If it's truly just a few lines, then I've misunderstood what you're
> suggesting (patches welcome). It's not the separator splitting that
> I'm worried about, but the restructuring of the test.
Here is a very slapdash attempt at pushing the "chunk size iteration"
part of the tests down into the test executable, using null
separators. I think it's ugly, but maybe not quite as bad as I feared.
Unfortunately it only gives about a 4x speedup on my machine, and I
was hoping for much more. (We should really expect this entire thing
to run in a fraction of a second.)
Let me know if you think the tradeoff is worth it for now; I can
polish it up if so.
Thanks,
--Jacob
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-WIP-try-adding-chunk-ranges.patch | application/octet-stream | 8.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Maciek Sakrejda | 2025-09-27 00:31:43 | Re: V18 change on EXPLAIN ANALYZE |
| Previous Message | Tom Lane | 2025-09-26 21:11:56 | Re: V18 change on EXPLAIN ANALYZE |