| From: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
|---|---|
| To: | Yoshimi Ichiyanagi <ichiyanagi(dot)yoshimi(at)lab(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
| Cc: | menjo(dot)takashi(at)lab(dot)ntt(dot)co(dot)jp, ishizaki(dot)teruaki(at)lab(dot)ntt(dot)co(dot)jp |
| Subject: | Re: [HACKERS][PATCH] Applying PMDK to WAL operations for persistent memory |
| Date: | 2018-03-01 10:40:05 |
| Message-ID: | 91411837-8c65-bf7d-7ca3-d69bdcb4968a@iki.fi |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 16/01/18 15:00, Yoshimi Ichiyanagi wrote:
> Hi.
>
> These patches enable to use Persistent Memory Development Kit(PMDK)[1]
> for reading/writing WAL logs on persistent memory(PMEM).
> PMEM is next generation storage and it has a number of nice features:
> fast, byte-addressable and non-volatile.
Interesting. How does this compare with using good old mmap()? I think
just doing that would allow eliminating much of the complexity around
managing the shared_buffers. And if the OS is smart about persistent
memory (I don't know what the state of the art on that is), presumably
msync() and fsync() on an file that lives in persistent memory is
lightning fast.
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-03-01 10:41:15 | Re: Failed to request an autovacuum work-item in silence |
| Previous Message | Andres Freund | 2018-03-01 10:36:41 | Re: [HACKERS][PATCH] Applying PMDK to WAL operations for persistent memory |