From: | Curt Sampson <cjs(at)cynic(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Kevin Brown <kevin(at)sysexperts(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: First set of OSDL Shared Mem scalability results, some |
Date: | 2004-10-25 00:30:56 |
Message-ID: | Pine.NEB.4.58.0410250926300.1004@angelic-vtfw.cvpn.cynic.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
On Sun, 24 Oct 2004, Tom Lane wrote:
> > 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?
There's a pretty big difference between few-hundred-bytes-on-write and
eight-kilobytes-with-every-read memory copy.
As for the queue allocation, again, I have no data to back this up, but
I don't think it would be as bad as BufMgrLock. Not every page will have
a write queue, and a "hot" page is only going to get one once. (If a
page has a write queue, you might as well leave it with the page after
flushing it, and get rid of it only when the page leaves memory.)
I see the OS issues related to mapping that much memory as a much bigger
potential problem.
cjs
--
Curt Sampson <cjs(at)cynic(dot)net> +81 90 7737 2974 http://www.NetBSD.org
Make up enjoying your city life...produced by BIC CAMERA
From | Date | Subject | |
---|---|---|---|
Next Message | Marc G. Fournier | 2004-10-25 00:36:53 | Beta4 Bundled ... |
Previous Message | Andrew Dunstan | 2004-10-24 23:56:54 | windows milestone |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-10-25 01:18:07 | Re: First set of OSDL Shared Mem scalability results, some |
Previous Message | Tom Lane | 2004-10-25 00:16:17 | Re: Reindexdb and REINDEX |