| From: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
|---|---|
| To: | arjun shetty <arjunshetty955(at)gmail(dot)com>, Imre Samu <pella(dot)samu(at)gmail(dot)com> |
| Cc: | "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PostgreSQLv14 TPC-H performance GCC vs Clang |
| Date: | 2021-11-05 17:29:37 |
| Message-ID: | 69584b92-7405-8d65-adb5-175439b3f95e@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jimmy A | 2021-11-07 22:27:14 | EXISTS by itself vs SELECT EXISTS much slower in query. |
| Previous Message | arjun shetty | 2021-11-05 12:07:40 | Re: PostgreSQLv14 TPC-H performance GCC vs Clang |