Re: PostgreSQLv14 TPC-H performance GCC vs Clang - Mailing list pgsql-performance

From Tomas Vondra
Subject Re: PostgreSQLv14 TPC-H performance GCC vs Clang
Date
Msg-id 69584b92-7405-8d65-adb5-175439b3f95e@enterprisedb.com
Whole thread Raw
In response to Re: PostgreSQLv14 TPC-H performance GCC vs Clang  (arjun shetty <arjunshetty955@gmail.com>)
Responses PostgreSQLv14 TPC-H performance GCC vs Clang  (arjun shetty <arjunshetty955@gmail.com>)
List pgsql-performance
Hi,

IMO this thread provides so little information it's almost impossible to 
answer the question. There's almost no information about the hardware, 
scale of the test, configuration of the Postgres instance, the exact 
build flags, differences in generated asm code, etc.

I find it hard to believe merely switching from clang to gcc yields 22% 
speedup - that's way higher than any differences we've seen in the past.

In my experience, the speedup is unlikely to be "across the board". 
There will be a handful of affected queries, while most remaining 
queries will be about the same. In that case you need to focus on those 
queries, see if the plans are the same, do some profiling, etc.


regards

-- 
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-performance by date:

Previous
From: arjun shetty
Date:
Subject: Re: PostgreSQLv14 TPC-H performance GCC vs Clang
Next
From: Jimmy A
Date:
Subject: EXISTS by itself vs SELECT EXISTS much slower in query.