From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Greg Stark <stark(at)mit(dot)edu>, Claudio Freire <klaussfreire(at)gmail(dot)com> |
Cc: | KONDO Mitsumasa <kondo(dot)mitsumasa(at)lab(dot)ntt(dot)co(dot)jp>, Tatsuo Ishii <ishii(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, PostgreSQL-Dev <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Why we are going to have to go DirectIO |
Date: | 2013-12-05 17:49:48 |
Message-ID: | 52A0BCBC.3000608@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 12/05/2013 07:40 AM, Greg Stark wrote:
> On Thu, Dec 5, 2013 at 2:54 PM, Claudio Freire <klaussfreire(at)gmail(dot)com> wrote:
>> That's a bad idea in the current state of affairs. MM files haven't
>> been designed for that usage, and getting stable performance out of
>> that will be way too difficult.
>
> I'm talking about long-term goals here. Either of these two routes
> would require whole new kernel interfaces to work effectively. Without
> those new kernel interfaces our current approach is possibly the best
> we can get.
Well, in the long run we'll probably be using persistent RAM. And the
geeks who manage that have already said that MMAP is a bad interface for
persistent RAM. They haven't defined a good one, though.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2013-12-05 17:54:36 | Re: Why we are going to have to go DirectIO |
Previous Message | David E. Wheeler | 2013-12-05 17:43:48 | Re: Proposal: variant of regclass |