aboutsummaryrefslogtreecommitdiff
path: root/src/tutorial/syscat.source
diff options
context:
space:
mode:
authorNathan Bossart <nathan@postgresql.org>2024-04-06 21:56:23 -0500
committerNathan Bossart <nathan@postgresql.org>2024-04-06 21:56:23 -0500
commit792752af4eb5cf7b5b8b0470dbf22901c5178fe5 (patch)
tree2090baf57be8c2bf773386571587aa6511d8cb27 /src/tutorial/syscat.source
parent158f5819236806b7c9cab323658c231e9371c458 (diff)
downloadpostgresql-792752af4eb5cf7b5b8b0470dbf22901c5178fe5.tar.gz
postgresql-792752af4eb5cf7b5b8b0470dbf22901c5178fe5.zip
Optimize pg_popcount() with AVX-512 instructions.
Presently, pg_popcount() processes data in 32-bit or 64-bit chunks when possible. Newer hardware that supports AVX-512 instructions can use 512-bit chunks, which provides a nice speedup, especially for larger buffers. This commit introduces the infrastructure required to detect compiler and CPU support for the required AVX-512 intrinsic functions, and it adds a new pg_popcount() implementation that uses these functions. If CPU support for this optimized implementation is detected at runtime, a function pointer is updated so that it is used by subsequent calls to pg_popcount(). Most of the existing in-tree calls to pg_popcount() should benefit from these instructions, and calls with smaller buffers should at least not regress compared to v16. The new infrastructure introduced by this commit can also be used to optimize visibilitymap_count(), but that is left for a follow-up commit. Co-authored-by: Paul Amonson, Ants Aasma Reviewed-by: Matthias van de Meent, Tom Lane, Noah Misch, Akash Shankaran, Alvaro Herrera, Andres Freund, David Rowley Discussion: https://postgr.es/m/BL1PR11MB5304097DF7EA81D04C33F3D1DCA6A%40BL1PR11MB5304.namprd11.prod.outlook.com
Diffstat (limited to 'src/tutorial/syscat.source')
0 files changed, 0 insertions, 0 deletions