pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: William Yu <wyu@talisys.com>
To: pgsql-performance@postgresql.org
Subject: Re: How to improve db performance with $7K?
Date: Wed, 06 Apr 2005 13:01:35 -0700
Message-ID: <d31f71$2epm$1@news.hub.org> (raw)
In-Reply-To: <33c6269f050406083533d2045d@mail.gmail.com>
References: <42443863.4040302@sfnet.cc>
	<42455DEC.2080301@sfnet.cc>
	<1112049794.23284.29.camel@localhost.localdomain>
	<424840AE.3050200@sfnet.cc>
	<op.sod768rgth1vuj@localhost>
	<42494741.7060806@fastcrypt.com>
	<33c6269f0504040643317b69cd@mail.gmail.com>
	<42515198.9090903@sfnet.cc>
	<33c6269f05040412126b5bc719@mail.gmail.com>
	<d30377$1jn8$1@news.hub.org>
	<33c6269f050406083533d2045d@mail.gmail.com>

It's the same money if you factor in the 3ware controller. Even without 
a caching controller, SCSI works good in multi-threaded IO (not 
withstanding crappy shit from Dell or Compaq). You can get such cards 
from LSI for $75. And of course, many server MBs come with LSI 
controllers built-in. Our older 32-bit production servers all use Linux 
software RAID w/ SCSI and there's no issues when multiple 
users/processes hit the DB.

*Maybe* a 3ware controller w/ onboard cache + battery backup might do 
much better for multi-threaded IO than just plain-jane SATA. 
Unfortunately, I have not been able to find anything online that can 
confirm or deny this. Hence, the choice is spend $$$ on the 3ware 
controller and hope it meets your needs -- or spend $$$ on SCSI drives 
and be sure.

Now if you want to run such tests, we'd all be delighted with to see the 
results so we have another option for building servers.


Alex Turner wrote:
> It's hardly the same money, the drives are twice as much.
> 
> It's all about the controller baby with any kind of dive.  A bad SCSI
> controller will give sucky performance too, believe me.  We had a
> Compaq Smart Array 5304, and it's performance was _very_ sub par.
> 
> If someone has a simple benchmark test database to run, I would be
> happy to run it on our hardware here.
> 
> Alex Turner
> 
> On Apr 6, 2005 3:30 AM, William Yu <wyu@talisys.com> wrote:
> 
>>Alex Turner wrote:
>>
>>>I'm no drive expert, but it seems to me that our write performance is
>>>excellent.  I think what most are concerned about is OLTP where you
>>>are doing heavy write _and_ heavy read performance at the same time.
>>>
>>>Our system is mostly read during the day, but we do a full system
>>>update everynight that is all writes, and it's very fast compared to
>>>the smaller SCSI system we moved off of.  Nearly a 6x spead
>>>improvement, as fast as 900 rows/sec with a 48 byte record, one row
>>>per transaction.
>>
>>I've started with SATA in a multi-read/multi-write environment. While it
>>ran pretty good with 1 thread writing, the addition of a 2nd thread
>>(whether reading or writing) would cause exponential slowdowns.
>>
>>I suffered through this for a week and then switched to SCSI. Single
>>threaded performance was pretty similar but with the advanced command
>>queueing SCSI has, I was able to do multiple reads/writes simultaneously
>>with only a small performance hit for each thread.
>>
>>Perhaps having a SATA caching raid controller might help this situation.
>>I don't know. It's pretty hard justifying buying a $$$ 3ware controller
>>just to test it when you could spend the same money on SCSI and have a
>>guarantee it'll work good under multi-IO scenarios.
>>
>>---------------------------(end of broadcast)---------------------------
>>TIP 8: explain analyze is your friend
>>
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
> 



view thread (119+ messages)  latest in thread

Message-ID: <d31f71$2epm$1@news.hub.org>
Permalink:  ../d31f71$2epm$1@news.hub.org/
Also on:    postgresql.org/message-id/d31f71$2epm$1@news.hub.org

 · 

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: wyu@talisys.com
  Subject: Re: How to improve db performance with $7K?
  In-Reply-To: <d31f71$2epm$1@news.hub.org>

* 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