From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
Cc: | sthomas(at)peak6(dot)com, Jim Nasby <jim(at)nasby(dot)net>, Anthony Presley <anthony(at)resolution(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Infinite Cache |
Date: | 2011-07-08 13:41:54 |
Message-ID: | CABUevEzn7PQXzS-km7A8v_0PUfCasMh9p1PLAtw6_jDZe15ODw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Fri, Jul 8, 2011 at 15:34, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> On 05.07.2011 16:35, Shaun Thomas wrote:
>>
>> I'd say it's probably safe enough these days. But it's also one of those
>> exclusive selling points they're using right now to garner EDB
>> customers. So I doubt it'll be released any time *soon*, though may make
>> it eventually.
>
> I doubt the community would want it even if it was open sourced. As an open
> source project, what would probably make more sense is a similar caching
> mechanism built into the kernel, somewhere between the filesystem cache and
> user-space. That way any you could use it with any application that benefits
> from the kind of large cache that Infinite Cache provides.
Don't underestimate how much easier it is to get something into an
environment as part of the database than as an extra module or app
that you have to patch your kernel with. Unless you can get it all the
way into the baseline kernel of course, but that's not going to be
easy...
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | D C | 2011-07-08 16:46:59 | Re: "VACUUM FULL ANALYZE" vs. Autovacuum Contention |
Previous Message | Jose Ildefonso Camargo Tolosa | 2011-07-08 13:37:45 | Re: [PERFORM] DELETE taking too much memory |