Make a 100_bugs.pl test more faster.

From: "Anton A(dot) Melnikov" <aamelnikov(at)inbox(dot)ru>
To: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Make a 100_bugs.pl test more faster.
Date: 2022-11-16 14:41:16
Message-ID: eb7aa992-c2d7-6ce7-4942-0c784231a362@inbox.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello!

The previous discussion was here:
https://www.postgresql.org/message-id/flat/b570c367-ba38-95f3-f62d-5f59b9808226%40inbox.ru

>On 15.11.2022 04:59, Tom Lane wrote:
>> "Anton A. Melnikov" <aamelnikov(at)inbox(dot)ru> writes:
>>
>> Additionally
>> i've tried to reduce overall number of nodes previously
>> used in this test in a similar way.
>
> Optimizing existing tests isn't an answer to that. We could
> install those optimizations without adding a new test case.

Here is a separate patch for the node usage optimization mentioned above.
It decreases the CPU usage during 100_bugs.pl by about 30%.

There are also some experimental data: 100_bugs-CPU-usage.txt

Would be glad for any comments and concerns.

With best regards,

--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

Attachment Content-Type Size
v1-0001-Reuse-nodes-in-100_bugs-test.patch text/x-patch 1.7 KB
100_bugs-CPU-usage.txt text/plain 2.0 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2022-11-16 14:45:48 Re: const qualifier for list APIs
Previous Message Ted Yu 2022-11-16 13:51:48 Re: closing file in adjust_data_dir