From: Kenneth Marshall <ktm@it.is.rice.edu>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Greg Stark <gsstark@MIT.EDU>
Cc: pgsql-hackers@postgresql.org
Subject: Re: [PATCHES] ARC Memory Usage analysis
Date: Mon, 25 Oct 2004 17:48:30 -0500
Message-ID: <20041025224830.GQ12041@it.is.rice.edu> (raw)
In-Reply-To: <790.1098741205@sss.pgh.pa.us>
References: <1098471059.20926.49.camel@localhost.localdomain>
<41796115.2020501@Yahoo.com>
<20041022200955.GC4382@it.is.rice.edu>
<417D1D01.3090401@Yahoo.com>
<20651.1098720192@sss.pgh.pa.us>
<87mzyavhxc.fsf@stark.xeocode.com>
<87hdoiv62b.fsf@stark.xeocode.com>
<790.1098741205@sss.pgh.pa.us>
On Mon, Oct 25, 2004 at 05:53:25PM -0400, Tom Lane wrote:
> Greg Stark <gsstark@MIT.EDU> writes:
> > So I would suggest using something like 100us as the threshold for
> > determining whether a buffer fetch came from cache.
>
> I see no reason to hardwire such a number. On any hardware, the
> distribution is going to be double-humped, and it will be pretty easy to
> determine a cutoff after minimal accumulation of data. The real question
> is whether we can afford a pair of gettimeofday() calls per read().
> This isn't a big issue if the read actually results in I/O, but if it
> doesn't, the percentage overhead could be significant.
>
How invasive would reading the "CPU counter" be, if it is available?
A read operation should avoid flushing a cache line and we can throw
out the obvious outliers since we only need an estimate and not the
actual value.
--Ken
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: ktm@it.is.rice.edu, tgl@sss.pgh.pa.us, gsstark@MIT.EDU, pgsql-hackers@postgresql.org
Subject: Re: [PATCHES] ARC Memory Usage analysis
In-Reply-To: <20041025224830.GQ12041@it.is.rice.edu>
* 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