Re: Stalls on PGSemaphoreLock

From: "Gudmundsson Martin (mg)" <martin(dot)mg(dot)gudmundsson(at)volvo(dot)com>
To: Pavy Philippe <Philippe(dot)Pavy(at)worldline(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Stalls on PGSemaphoreLock
Date: 2014-03-27 07:38:51
Message-ID: 2E5766F28426E547AF0A2A870FAE630D22EAC0@SEGOTNC5182-N2.vcn.ds.volvo.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Hi Pavy!
What kernel version/RHEL release are you running on the servers you are experiencing these issues?
I'm interested in knowing since I suspect similar issues on some of our database servers.

Best regards, Martin

> -----Original Message-----
> From: pgsql-performance-owner(at)postgresql(dot)org [mailto:pgsql-performance-
> owner(at)postgresql(dot)org] On Behalf Of Pavy Philippe
> Sent: den 25 mars 2014 9:10
> To: Matthew Spilich; pgsql-performance(at)postgresql(dot)org
> Subject: Re: [PERFORM] Stalls on PGSemaphoreLock
>
> Here, we were the transparent hugepage always actif:
> cat /sys/kernel/mm/redhat_transparent_hugepage/enabled
> [always] never
>
> We changed to:
> cat /sys/kernel/mm/redhat_transparent_hugepage/enabled
> always [never]
>
>
>
> For the semaphore, our initial configuration was:
> cat /proc/sys/kernel/sem
> 250 32000 32 128
>
> And we changed to:
> cat /proc/sys/kernel/sem
> 5010 641280 5010 128
>

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Dave Johansen 2014-03-27 20:42:39 Partitions and prepared statements?
Previous Message Josh Berkus 2014-03-27 00:35:11 Re: Connection pooling - Number of connections