pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Brian Hurt <bhurt@janestcapital.com>
To: Bryan Murphy <bryan.murphy@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: SAN vs Internal Disks
Date: Fri, 07 Sep 2007 14:21:52 -0400
Message-ID: <46E196C0.5020508@janestcapital.com> (raw)
In-Reply-To: <bd8531800709071056g740cb44cld04cd489bc4e6343@mail.gmail.com>
References: <a199704d0709060535q6fea139aq2e3863e685555b0d@mail.gmail.com>
	<dcc563d10709060925o6f11f632sbfbc2b64530ae80d@mail.gmail.com>
	<a199704d0709061003u71d536fbh9d71ed095dfe16b@mail.gmail.com>
	<Pine.GSO.4.64.0709062354040.28915@westnet.com>
	<20070907100446.GE1795@mathom.us>
	<20070907103341.GC20896@oppetid.no>
	<46E18886.7060502@aptalaska.net>
	<bd8531800709071056g740cb44cld04cd489bc4e6343@mail.gmail.com>

Bryan Murphy wrote:

>Our database server connects to the san via iSCSI over Gig/E using
>jumbo frames.  File system is XFS (noatime).
>
>
>  
>
...

>Throughput, however, kinda sucks.  I just can't get the kind of
>throughput to it I was hoping to get.  When our memory cache is blown,
>the database can be downright painful for the next few minutes as
>everything gets paged back into the cache.
>
>  
>

Remember that Gig/E is bandwidth limited to about 100 Mbyte/sec.  Maybe 
a little faster than that downhill with a tailwind, but not much.  
You're going to get much better bandwidth connecting to a local raid 
card talking to local disks simply due to not having the ethernet as a 
bottleneck.  iSCSI is easy to set up and manage, but it's slow.  This is 
the big advantage Fibre Channel has- serious performance.  You can have 
multiple channels on a single fibre channel card- IIRC, QLogic's cards 
have a default of 4 channels- each pumping 400 Mbyte/sec.  At which 
point the local bus rapidly becomes the bottleneck.  Of course, this 
comes at the cost of a signifigant increase in complexity.

Brian




view thread (37+ messages)  latest in thread

Message-ID: <46E196C0.5020508@janestcapital.com>
Permalink:  ../46E196C0.5020508@janestcapital.com/
Also on:    postgresql.org/message-id/46E196C0.5020508@janestcapital.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: bhurt@janestcapital.com, bryan.murphy@gmail.com
  Subject: Re: SAN vs Internal Disks
  In-Reply-To: <46E196C0.5020508@janestcapital.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