From: Jan Wieck <JanWieck@Yahoo.com>
To: Greg Stark <gsstark@mit.edu>
Cc: Christopher Browne <cbbrowne@acm.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: First set of OSDL Shared Mem scalability results, some
Date: Thu, 14 Oct 2004 00:29:19 -0400
Message-ID: <416E009F.3010709@Yahoo.com> (raw)
In-Reply-To: <87sm8i3p4f.fsf@stark.xeocode.com>
References: <200410081443.16109.josh@agliodbs.com>
<m31xg8zlo4.fsf@wolfe.cbbrowne.com>
<416DCCFF.70304@Yahoo.com>
<871xg25538.fsf@stark.xeocode.com>
<416DFDDE.5070600@Yahoo.com>
<87sm8i3p4f.fsf@stark.xeocode.com>
On 10/14/2004 12:22 AM, Greg Stark wrote:
> Jan Wieck <JanWieck@Yahoo.com> writes:
>
>> Which would require that shared memory is not allowed to be swapped out, and
>> that is allowed in Linux by default IIRC, not to completely distort the entire
>> test.
>
> Well if it's getting swapped out then it's clearly not being used effectively.
Is it really that easy if 3 different cache algorithms (PG cache, kernel
buffers and swapping) are competing for the same chips?
Jan
>
> There are APIs to bar swapping out pages and the tests could be run without
> swap. I suggested it only as an experiment though, there are lots of details
> between here and having it be a good configuration for production use.
>
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck@Yahoo.com #
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: JanWieck@Yahoo.com, gsstark@mit.edu, cbbrowne@acm.org
Subject: Re: First set of OSDL Shared Mem scalability results, some
In-Reply-To: <416E009F.3010709@Yahoo.com>
* 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