Re: test_json_parser/002_inline is kind of slow

From: Nathan Bossart <nathandbossart(at)gmail(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:25:19
Message-ID: aNawX3kfXzeSWmrv@nathan
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Sep 26, 2025 at 11:11:52AM -0400, Robert Haas wrote:
> I've noticed that when I run 'meson test', the test mentioned in the
> subject line is usually the last one to finish. The test runs for 22
> seconds on my machine, which is fairly high considering that 'meson
> test' in total (and with MESON_TESTTHREADS=8) runs for 3 minutes and
> 13 seconds. I think the reason for this relatively high runtime is
> that it fires off a separate shell command for each separate test, and
> there are 3400 of those. I'm not exactly sure what change to propose,
> but I wonder if we could come up with a way of making this a bit more
> efficient? 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.

For some slow tests, we just have meson start it earlier with something
like this:

+ 'test_kwargs': {'priority': 40},

At least, that's enough to prevent it from completing last on my machine.
But actually improving the efficiency of the test seems like a better
long-term fix.

--
nathan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David G. Johnston 2025-09-26 15:32:46 Re: Avoiding roundoff error in pg_sleep()
Previous Message Vladlen Popolitov 2025-09-26 15:25:09 Re: Avoiding roundoff error in pg_sleep()