From: Shaun Thomas <sthomas@optionshouse.com>
To: Dave Johansen <davejohansen@gmail.com>
Cc: pgsql-performance <pgsql-performance@postgresql.org>
Subject: Re: Unexpected pgbench result
Date: Fri, 20 Dec 2013 08:10:32 -0600
Message-ID: <52B44FD8.2030105@optionshouse.com> (raw)
In-Reply-To: <CAAcYxUd7sm6L6p3=bWiFPRm8qpvEu59zHuwtv_ni-HAgHO0PQw@mail.gmail.com>
References: <CAAcYxUe11Qdx7h3RaRjuGGvp3oO7Wi-QNYrN=9TXBSv+P2u0hg@mail.gmail.com>
<52B33069.1060203@optionshouse.com>
<CAAcYxUd7sm6L6p3=bWiFPRm8qpvEu59zHuwtv_ni-HAgHO0PQw@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
On 12/19/2013 04:06 PM, Dave Johansen wrote:
> Right now, we're running a RAID 1 for pg_clog, pg_log and pg_xlog and
> then a RAID 1+0 with 12 disks for the data. Would there be any benefit
> to running a separate RAID 1+0 with a tablespace for the indexes?
Not really. PostgreSQL doesn't currently support parallel backend
fetches, aggregation, or really anything. It's looking like 9.4 will get
us a lot closer to that, but right now, everything is serial.
Serial or not, separate backends will have separate read concerns, and
PostgreSQL 9.2 and above *do* support index only scans. So
theoretically, you might actually see some benefit there. If it were me
and I had spindles available, I would just increase the overall size of
the pool. It's a lot easier than managing multiple tablespaces.
--
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604
312-676-8870
sthomas@optionshouse.com
______________________________________________
See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
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: sthomas@optionshouse.com, davejohansen@gmail.com
Subject: Re: Unexpected pgbench result
In-Reply-To: <52B44FD8.2030105@optionshouse.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