Re: Avoid multiple calls to memcpy (src/backend/access/index/genam.c) - Mailing list pgsql-hackers

From Ranier Vilela
Subject Re: Avoid multiple calls to memcpy (src/backend/access/index/genam.c)
Date
Msg-id CAEudQArStWAwxLM6ORNo2YtJ=Uw-MNRv9B-k_gQ6O=yt=7GtAA@mail.gmail.com
Whole thread
In response to Re: Avoid multiple calls to memcpy (src/backend/access/index/genam.c)  (lakshmi <lakshmigcdac@gmail.com>)
Responses Re: Avoid multiple calls to memcpy (src/backend/access/index/genam.c)
List pgsql-hackers
Hi.

Em seg., 23 de mar. de 2026 às 01:42, lakshmi <lakshmigcdac@gmail.com> escreveu:
Hi,

Thanks for the reply.

Here are the details of my test setup.

I ran the tests on Debian Linux (6.1.0-10-amd64, x86_64) on an AMD Ryzen 5 7535U (6 cores / 12 threads).
Thanks for the tests. 

The PostgreSQL version was 19devel, built from source using gcc 12.2.0 with enable-debug.

For benchmarking, I used pgbench with the following command:
pgbench -p 55432 -d postgres -c 10 -j 4 -T 60

The database was initialized with scale factor 1 (pgbench -i). I ran multiple iterations for both the original and patched versions and compared TPS and latency across runs.

All tests were done on the same system under similar conditions.

Please let me know if you’d like me to try any other scenarios or provide more details.
Could you repeat the tests without enable-debug?

best regards,
Ranier Vilela

pgsql-hackers by date:

Previous
From: Isaac Morland
Date:
Subject: Re: Read-only connection mode for AI workflows.
Next
From: Jakub Wartak
Date:
Subject: Re: Add pg_stat_vfdcache view for VFD cache statistics