On Mon, Jul 27, 2020 at 2:45 PM Thomas Munro wrote:
> Here's a new version, using the name min_dynamic_shared_memory, which
> sounds better to me. Any objections? I also fixed the GUC's maximum
> setting so that it's sure to fit in size_t.
I pushed it like that. Happy to rename the GUC if
also fixed the GUC's maximum
setting so that it's sure to fit in size_t.
From 3a77e8ab67e5492340425f1ce4a36a45a8c80d05 Mon Sep 17 00:00:00 2001
From: Thomas Munro
Date: Mon, 27 Jul 2020 12:07:05 +1200
Subject: [PATCH v3] Preallocate some DSM space at startup.
Create an optional region in the
Hi,
On 2020-06-19 17:42:41 +1200, Thomas Munro wrote:
> On Thu, Jun 18, 2020 at 6:05 PM Thomas Munro wrote:
> > Here's a version that adds some documentation.
>
> I jumped on a dual socket machine with 36 cores/72 threads and 144GB
> of RAM (Azure F72s_v2) running Linux, configured with 50GB of
On Thu, Jun 18, 2020 at 6:05 PM Thomas Munro wrote:
> Here's a version that adds some documentation.
I jumped on a dual socket machine with 36 cores/72 threads and 144GB
of RAM (Azure F72s_v2) running Linux, configured with 50GB of huge
pages available, and I ran a very simple test: select
e at startup.
Create an optional region in the main shared memory segment that can be
used to acquire and release "fast" DSM segments, and can benefit from
huge pages allocated at cluster startup time, if configured. Fall back
to the existing mechanisms when
On Tue, Jun 9, 2020 at 6:03 PM Thomas Munro wrote:
> That all makes sense. Now I'm wondering if I should use exactly that
> word in the GUC... dynamic_shared_memory_preallocate?
I tend to prefer verb-object rather than object-verb word ordering,
because that's how English normally works, but I
ion that supplies memory for "fast" DSM
> > segments. When there isn't enough free space, dsm_create() falls back
> > to the traditional approach using eg shm_open().
>
> I think this is a reasonable option to have available for people who
> want to use it. I didn't want to
On Thu, Apr 9, 2020 at 1:46 AM Thomas Munro wrote:
> The attached highly experimental patch adds a new GUC
> dynamic_shared_memory_main_size. If you set it > 0, it creates a
> fixed sized shared memory region that supplies memory for "fast" DSM
> segments. When ther
for one),
but that's not the only problem I wanted to attack.
The attached highly experimental patch adds a new GUC
dynamic_shared_memory_main_size. If you set it > 0, it creates a
fixed sized shared memory region that supplies memory for "fast" DSM
segments. When there isn't enou
