| From: | William Yu <wyu(at)talisys(dot)com> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: How to improve db performance with $7K? |
| Date: | 2005-04-06 07:30:44 |
| Message-ID: | d30377$1jn8$1@news.hub.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2005-04-06 08:09:58 | Re: Sustained inserts per sec ... ? |
| Previous Message | bsimon | 2005-04-06 07:17:15 | RE : RE: Postgresql vs SQLserver for this application ? |