Skip site navigation (1) Skip section navigation (2)

Re: First set of OSDL Shared Mem scalability results, some wierdness ...

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kevin Brown <kevin(at)sysexperts(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: First set of OSDL Shared Mem scalability results, some wierdness ...
Date: 2004-10-09 15:07:28
Message-ID: 27696.1097334448@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-performance
Kevin Brown <kevin(at)sysexperts(dot)com> writes:
> This is why I sometimes wonder whether or not it would be a win to use
> mmap() to access the data and index files -- 

mmap() is Right Out because it does not afford us sufficient control
over when changes to the in-memory data will propagate to disk.  The
address-space-management problems you describe are also a nasty
headache, but that one is the showstopper.

			regards, tom lane

In response to

Responses

pgsql-performance by date

Next:From: Kevin BrownDate: 2004-10-09 20:37:12
Subject: Re: First set of OSDL Shared Mem scalability results, some wierdness ...
Previous:From: MatthewDate: 2004-10-09 15:02:09
Subject: Re: First set of OSDL Shared Mem scalability results, some

pgsql-hackers by date

Next:From: Tom LaneDate: 2004-10-09 15:19:51
Subject: Re: beta3 on unixware 714
Previous:From: MatthewDate: 2004-10-09 15:02:09
Subject: Re: First set of OSDL Shared Mem scalability results, some

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group