| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ashkil Dighin <ashkildighin76(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Lock contention high |
| Date: | 2021-11-15 15:25:31 |
| Message-ID: | 2123130.1636989931@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Ashkil Dighin <ashkildighin76(at)gmail(dot)com> writes:
> I suspect lock contention and performance issues with __int128. And I would
> like to check the performance by forcibly disabling int128(Maxalign16bytes)
> and enable like long long(maxlign 8bytes).
> Is it possible to disable int128 in PostgreSQL?
Sure, you can build without it --- easiest way would be to modify
pg_config.h after the configure step. But the idea that it has
something to do with lock contention seems like nonsense.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Creager | 2021-11-16 04:43:25 | Need help identifying a periodic performance issue. |
| Previous Message | Rick Otten | 2021-11-15 14:17:14 | Re: postgresql13-llvm jit-13.5-1PGDG.rhel8.x86_64 |