Re: [PATCHES] ARC Memory Usage analysis - Mailing list pgsql-hackers

From Curt Sampson
Subject Re: [PATCHES] ARC Memory Usage analysis
Date
Msg-id Pine.NEB.4.58.0410261502510.13312@angelic-vtfw.cvpn.cynic.net
Whole thread Raw
In response to Re: [PATCHES] ARC Memory Usage analysis  (Greg Stark <gsstark@mit.edu>)
Responses Re: [PATCHES] ARC Memory Usage analysis
List pgsql-hackers
On Tue, 26 Oct 2004, Greg Stark wrote:

> I see mmap or O_DIRECT being the only viable long-term stable states. My
> natural inclination was the former but after the latest thread on the subject
> I suspect it'll be forever out of reach. That makes O_DIRECT And a Postgres
> managed cache the only real choice. Having both caches is just a waste of
> memory and a waste of cpu cycles.

I don't see why mmap is any more out of reach than O_DIRECT; it's not
all that much harder to implement, and mmap (and madvise!) is more
widely available.

But if using two caches is only costing us 1% in performance, there's
not really much point....

cjs
-- 
Curt Sampson  <cjs@cynic.net>   +81 90 7737 2974   http://www.NetBSD.org    Make up enjoying your city life...produced
byBIC CAMERA
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCHES] ARC Memory Usage analysis
Next
From: Fabien COELHO
Date:
Subject: Re: Using ALTER TABLESPACE in pg_dump