RE: Shared Memory: How to use SYSV rather than MMAP ? - Mailing list pgsql-hackers

From REIX, Tony
Subject RE: Shared Memory: How to use SYSV rather than MMAP ?
Date
Msg-id HE1PR0202MB281226856BEB3DBA027D59BE86D90@HE1PR0202MB2812.eurprd02.prod.outlook.com
Whole thread Raw
In response to Re: Shared Memory: How to use SYSV rather than MMAP ?  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Shared Memory: How to use SYSV rather than MMAP ?
List pgsql-hackers

Hi Robert,


YES ! Reading this file, your suggestion should work ! Thx !

I've rebuilt and run the basic tests. We'll relaunch our tests asap.

Cordialement,

Tony Reix

tony.reix@atos.net

ATOS / Bull SAS
ATOS Expert
IBM Coop Architect & Technical Leader
Office : +33 (0) 4 76 29 72 67
1 rue de Provence - 38432 Échirolles - France

De : Robert Haas <robertmhaas@gmail.com>
Envoyé : mardi 20 novembre 2018 15:53:11
À : REIX, Tony
Cc : pgsql-hackers@postgresql.org; EMPEREUR-MOT, SYLVIE
Objet : Re: Shared Memory: How to use SYSV rather than MMAP ?
 
On Tue, Nov 20, 2018 at 8:36 AM REIX, Tony <tony.reix@atos.net> wrote:
> We are trying to understand why pgbench on AIX is slower compared to Linux/Power on the same HW/Disks.
>
> So, we have yet no idea about what may be the root cause and what should be changed.
>
> So, changing:     dynamic_shared_memory_type = sysv    seems to help.
>
> And maybe changing the main shared memory segment could also improve the performance. However, how one can change this?

There's no configuration setting for the main shared memory segment,
but removing #define USE_ANONYMOUS_SHMEM from sysv_shmem.c would
probably do the trick.

--
Robert Haas
EnterpriseDB: https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.enterprisedb.com&amp;data=01%7C01%7Ctony.reix%40atos.net%7C723ccf057a79436bcf9208d64ef7f48b%7C33440fc6b7c7412cbb730e70b0198d5a%7C0&amp;sdata=ZBRv1Ja1THRJH2symVaZSLjGQ4f9hRP9kw27hFlPdAE%3D&amp;reserved=0
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Patch to avoid SIGQUIT accident
Next
From: Alvaro Herrera
Date:
Subject: Re: incorrect xlog.c coverage report