Dear hackers,

I made another WIP patchset to mmap WAL segments as WAL buffers.  Note that 
this is not a non-volatile WAL buffer patchset but its competitor.  I am 
measuring and analyzing the performance of this patchset to compare with my 
N.V.WAL buffer.

Please wait for a several more days for the result report...

Best regards,
Takashi

-- 
Takashi Menjo <takashi.menjou...@hco.ntt.co.jp>
NTT Software Innovation Center

> -----Original Message-----
> From: Robert Haas <robertmh...@gmail.com>
> Sent: Wednesday, January 29, 2020 6:00 AM
> To: Takashi Menjo <takashi.menjou...@hco.ntt.co.jp>
> Cc: Heikki Linnakangas <hlinn...@iki.fi>; pgsql-hack...@postgresql.org
> Subject: Re: [PoC] Non-volatile WAL buffer
> 
> On Tue, Jan 28, 2020 at 3:28 AM Takashi Menjo 
> <takashi.menjou...@hco.ntt.co.jp> wrote:
> > I think our concerns are roughly classified into two:
> >
> >  (1) Performance
> >  (2) Consistency
> >
> > And your "different concern" is rather into (2), I think.
> 
> Actually, I think it was mostly a performance concern (writes triggering lots 
> of reading) but there might be a
> consistency issue as well.
> 
> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company

Attachment: 0001-Preallocate-more-WAL-segments.patch
Description: Binary data

Attachment: 0002-Use-WAL-segments-as-WAL-buffers.patch
Description: Binary data

Attachment: 0003-Lazy-unmap-WAL-segments.patch
Description: Binary data

Attachment: 0004-Speculative-map-WAL-segments.patch
Description: Binary data

Attachment: 0005-Allocate-WAL-segments-to-utilize-hugepage.patch
Description: Binary data

Reply via email to