Re: SAN vs Internal Disks - Mailing list pgsql-performance

From Greg Smith
Subject Re: SAN vs Internal Disks
Date
Msg-id Pine.GSO.4.64.0709071542280.25508@westnet.com
Whole thread Raw
In response to Re: SAN vs Internal Disks  (Tobias Brox <tobias@nordicbet.com>)
List pgsql-performance
On Fri, 7 Sep 2007, Tobias Brox wrote:

> We're also considering to install postgres on SAN - that is, my boss is
> convinced this is the right way to go.
> Advantages:
> 1. Higher I/O (at least the salesman claims so)

Shockingly, the salesman is probably lying to you.  The very concept of
SAN says that you're putting something in between your system and the
disks, and that something therefore must slow things down compared to
connecting directly.  iSCSI, FC, whatever you're using as the
communications channel can't be as fast as a controller card with a good
interface straight into the motherboard.  For example, a PCI-E x16 disk
controller card maxes out at 4GB/s in each direction; good luck bonding
enough iSCSI or FC channels together to reach that transfer rate and
getting something even remotely cost-competative with an internal card.

The cases where a SAN can improve upon performance over direct discs are
when the comparison isn't quite fair; for example:

1) The SAN allows spreading the load over more disks than you can fit
internally in the system
2) The SAN provides a larger memory cache than the internal cards you're
comparing against

If you're in one of those situations, then perhaps the salesman's claim
could have some merit.  There are lots of reasons one might want to use a
SAN, but a higher I/O rate when fairly comparing to connecting disks
directly is unlikely to be on that list.

--
* Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD

pgsql-performance by date:

Previous
From: Simon Riggs
Date:
Subject: Re: DRBD and Postgres: how to improve the perfomance?
Next
From: Vivek Khera
Date:
Subject: Re: SAN vs Internal Disks