Postgres process count GCC vs Clang is Different on autovaccum=on

From: hpc researcher_mspk <hpcresearch(dot)mspk(at)gmail(dot)com>
To: pgsql-performance(at)lists(dot)postgresql(dot)org
Subject: Postgres process count GCC vs Clang is Different on autovaccum=on
Date: 2021-11-24 12:05:50
Message-ID: CAL_6wb0EVzKQGWK0drJwXT2NJD1aqUA_azFDbxGtCSQ34YhHdw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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
vu GCC Clang
32 43 42
64 76 74
192 203 202
250 262 262
Case2:AutoVaccum=off
vu GCC Clang
32 40 40
64 72 72
192 200 200
250 261 263
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

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Thomas Kellerer 2021-11-24 12:10:45 Re: Out of memory error
Previous Message aditya desai 2021-11-24 07:35:14 Re: Out of memory error