Not using PostGIS
On Thursday, October 14, 2021, Paul Friedman <
paul.fried...@streetlightdata.com> wrote:
> Are you using PostGIS?
>
> If so, there is an issue with TOAST table locking having these symptoms.
>
>
> ---Paul
>
>
> On Wed, Oct 13, 2021 at 11:15 AM MichaelDBA
> wrote:
>
>> 1.Is ther
NUMA node0 CPU(s): 0-63,128-191NUMA node1 CPU(s): 64-127,192-255
Thread(s) per core: 2
Core(s) per socket: 64
Socket(s): 2
NUMA node(s):2
corepinning(ta perf lock contention results for 24,32 vu
0-63
24: 18.03% postgres postgres[.] LWLockAcquire
32: 7.02%
Hi
Captured the concurrent session with Netsat and pg-stat-actvity. Is the
procedure the right way to capture concurrent sesssions in postgresql?
netstat -a | grep postgres tcp 0 0 0.0.0.0:postgres 0.0.0.0:* LISTEN tcp 0
0 :postgres :53984 ESTABLISHED tcp 0 0 :postgres :54012 ESTABLISHED tcp 0
74
Ashkil,
Can you bind postgres in single NUMA node, for instance:
$ taskset -pc 0-63
Then run your benchmark, compare results in terms of benchmark metrics &
presence on LWLock(Acquire|Release) in perf top.
BR,
Michael.
On 10/14/21 9:45 AM, Ashkil Dighin wrote:
NUMA node0 CPU(s): 0-63,
