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
Date: Sun, 24 Oct 2004 10:39:35 -0400
Message-ID: <8438.1098628775@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.NEB.4.58.0410241442150.1004@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>
<26467.1098555064@sss.pgh.pa.us>
<Pine.NEB.4.58.0410241442150.1004@angelic-vtfw.cvpn.cynic.net>
Curt Sampson <cjs@cynic.net> writes:
> On Sat, 23 Oct 2004, Tom Lane wrote:
>> Seems to me the overhead of any such scheme would swamp the savings from
>> avoiding kernel/userspace copies ...
> Well, one really can't know without testing, but memory copies are
> extremely expensive if they go outside of the cache.
Sure, but what about all the copying from write queue to page?
>> the locking issues alone would be painful.
> I don't see why they would be any more painful than the current locking
> issues.
Because there are more locks --- the write queue data structure will
need to be locked separately from the page. (Even with a separate write
queue per page, there will need to be a shared data structure that
allows you to allocate and find write queues, and that thing will be a
subject of contention. See BufMgrLock, which is not held while actively
twiddling the contents of pages, but is a serious cause of contention
anyway.)
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
In-Reply-To: <8438.1098628775@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