From: Tom Lane <tgl@sss.pgh.pa.us>
To: Curt Sampson <cjs@cynic.net>
Cc: Kevin Brown <kevin@sysexperts.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: First set of OSDL Shared Mem scalability results, some wierdness ...
Date: Sat, 23 Oct 2004 14:11:04 -0400
Message-ID: <26467.1098555064@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.NEB.4.58.0410231627240.1876@angelic-vtfw.cvpn.cynic.net>
References: <200410081443.16109.josh@agliodbs.com>
<m31xg8zlo4.fsf@wolfe.cbbrowne.com>
<20041009112048.GA665@filer>
<27696.1097334448@sss.pgh.pa.us>
<20041009203710.GB665@filer>
<4859.1097363137@sss.pgh.pa.us>
<Pine.NEB.4.58.0410231627240.1876@angelic-vtfw.cvpn.cynic.net>
Curt Sampson <cjs@cynic.net> writes:
> Back when I was working out how to do this, I reckoned that you could
> use mmap by keeping a write queue for each modified page. Reading,
> you'd have to read the datum from the page and then check the write
> queue for that page to see if that datum had been updated, using the
> new value if it's there. Writing, you'd add the modified datum to the
> write queue, but not apply the write queue to the page until you'd had
> confirmation that the corresponding transaction log entry had been
> written. So multiple writes are no big deal; they just all queue up in
> the write queue, and at any time you can apply as much of the write
> queue to the page itself as the current log entry will allow.
Seems to me the overhead of any such scheme would swamp the savings from
avoiding kernel/userspace copies ... the locking issues alone would be
painful.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, cjs@cynic.net, kevin@sysexperts.com
Subject: Re: First set of OSDL Shared Mem scalability results, some wierdness ...
In-Reply-To: <26467.1098555064@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox