Postgres process count GCC vs Clang is Different on autovaccum=on - Mailing list pgsql-performance

From hpc researcher_mspk
Subject Postgres process count GCC vs Clang is Different on autovaccum=on
Date
Msg-id CAL_6wb0EVzKQGWK0drJwXT2NJD1aqUA_azFDbxGtCSQ34YhHdw@mail.gmail.com
Whole thread Raw
Responses Re: Postgres process count GCC vs Clang is Different on autovaccum=on  (Tomas Vondra <tomas.vondra@enterprisedb.com>)
List pgsql-performance
Software/Hardware used:
===================
PostgresV14.v
OS: RHELv8.4
Benchmark:HammerDB v4.3
Hardware used: Apple/AMD Ryzen.
RAM size: 256 GB
SSD/HDD: 1TB
CPU(s): 256(0-255)
Thread(s) per core:  2
Core(s) per socket:  64
Socket(s):           2
NUMA node(s):        8

Command used to count process: ps -eaf | grep postgres

Case1: AutoVaccum=on
vuGCCClang
324342
647674
192203202
250262262

Case2:AutoVaccum=off
vuGCCClang
324040
647272
192200200
250261263

In Case1 why is the process different in Clang vs GCC.
In postgresql process dependent wrt compiler GCC/Clang?
Is any recommendation or suggestion to check on this in Postgresv14


pgsql-performance by date:

Previous
From: aditya desai
Date:
Subject: Re: Out of memory error
Next
From: Thomas Kellerer
Date:
Subject: Re: Out of memory error