From: Greg Smith <gsmith@gregsmith.com>
To: Matthew <matthew@flymine.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: Strange behavior: pgbench and new Linux kernels
Date: Fri, 18 Apr 2008 13:19:09 -0400 (EDT)
Message-ID: <Pine.GSO.4.64.0804181317480.6528@westnet.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0804181144150.12158@aragorn.flymine.org>
References: <Pine.GSO.4.64.0804170230180.26917@westnet.com>
<Pine.LNX.4.64.0804171538200.20402@aragorn.flymine.org>
<Pine.LNX.4.64.0804181144150.12158@aragorn.flymine.org>
On Fri, 18 Apr 2008, Matthew wrote:
> You may also be seeing processes forced to switch between CPUs, which
> breaks the caches even more. So what happens if you run pgbench on a
> separate machine to the server? Does the problem still exist in that
> case?
I haven't run that test yet but will before I submit a report. I did
however try running things with the pgbench executable itself bound to a
single CPU with no improvement.
--
* Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD
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: gsmith@gregsmith.com, matthew@flymine.org
Subject: Re: Strange behavior: pgbench and new Linux kernels
In-Reply-To: <Pine.GSO.4.64.0804181317480.6528@westnet.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