Re: test_json_parser/002_inline is kind of slow

From: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: test_json_parser/002_inline is kind of slow
Date: 2025-09-26 15:33:08
Message-ID: CAOYmi+=yRU+nRBar6fecZKKenFyOgJWDf2DOyFD0gGKz86Lpvg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Sep 26, 2025 at 8:12 AM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> Basically anything that would allow us to do multiple tests
> without having to fork a new process for every single one seems like
> it would probably save quite a bit.

Agreed, it's pretty inefficient. (For comparison, it runs in about two
seconds on my machine, so I hadn't noticed how bad it had gotten.
Thanks for pointing it out.)

The hammer I had available at the time was
Perl-plus-compiled-executable. But I've just recently added a C-based
TAP suite in 4e1e417330d4, so I could try to port this suite over in
that direction. (Or I could find a way to port it to pytest... but C
seems like a better fit for testing the parser, in part because it'll
be more easily fuzzable that way.)

--Jacob

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2025-09-26 15:35:49 Re: test_json_parser/002_inline is kind of slow
Previous Message David G. Johnston 2025-09-26 15:32:46 Re: Avoiding roundoff error in pg_sleep()