pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Marty Jia <mjia@ask.com>
Cc: Mark Lewis <mark.lewis@mir3.com>
Cc: pgsql-performance@postgresql.org, DBAs <DBAs@ask.com>
Cc: Rich Wilson <richwilson@ask.com>
Cc: Ernest Wurzbach <EWurzbach@ask.com>
Subject: Re: How to get higher tps
Date: Tue, 22 Aug 2006 10:26:41 -0500
Message-ID: <1156260401.7223.14.camel@state.g2switchworks.com> (raw)
In-Reply-To: <0B9A8C89DCC3AB488A78A4DE0FECDA90019E31DF@SITE3MAIL04.jeeves.ask.info>
References: <0B9A8C89DCC3AB488A78A4DE0FECDA90019E31DF@SITE3MAIL04.jeeves.ask.info>

On Tue, 2006-08-22 at 08:16, Marty Jia wrote:
> Hi, Mark
> 
> Thanks, here is our hardware info:
> 
> RAID 10, using 3Par virtual volume technology across ~200 physical FC
> disks.  4 virtual disks for PGDATA, striped with LVM into one volume, 2
> virtual disks for WAL, also striped.  SAN attached with Qlogic SAN
> surfer multipathing to load balance each LUN on two 2GBs paths.  HBAs
> are Qlogic 2340's.  16GB host cache on 3Par.

A few points.  

Someone (Luke I think) posted that Linux's LVM has a throughput limit of
around 600 Megs/second.

Why are you using multiple virtual disks on an LPAR?  Did you try this
with just a single big virtual disk first to have something to compare
it to?  I think your disk subsystem is overthought for an LPAR.  If you
were running physical disks on a locally attached RAID card, it would be
a good idea.  But here you're just adding layers of complexity for no
gain, and in fact may be heading backwards.

I'd make two volumes on the LPAR, and let the LPAR do all the
virtualization for you.  Put a couple disks in a mirror set for the
pg_xlog, format it ext2, and mount it noatime.  Make another from a
dozen or so disks in an RAID 0 on top of RAID 1 (i.e. make a bunch of
mirror sets and stripe them into one big partition) and mount that for
PGDATA.  Simplify, and get a baseline.  Then, start mucking about to see
if you can get better performance.  change ONE THING at a time, and only
one thing, and test it well.

Got the latest and greatest drivers for the qlogic cards?

I would suggest some component testing to make sure everything is
working well.  bonnie++ and dd come to mind.



view thread (23+ messages)  latest in thread

Message-ID: <1156260401.7223.14.camel@state.g2switchworks.com>
Permalink:  ../1156260401.7223.14.camel@state.g2switchworks.com/
Also on:    postgresql.org/message-id/1156260401.7223.14.camel@state.g2switchworks.com

 · 

reply

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: smarlowe@g2switchworks.com, mjia@ask.com, mark.lewis@mir3.com, DBAs@ask.com, richwilson@ask.com, EWurzbach@ask.com
  Subject: Re: How to get higher tps
  In-Reply-To: <1156260401.7223.14.camel@state.g2switchworks.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