| From: | "Mohan, Ross" <RMohan(at)arbinet(dot)com> |
|---|---|
| To: | <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: How to improve db performance with $7K? |
| Date: | 2005-04-19 16:12:44 |
| Message-ID: | CC74E7E10A8A054798B6611BD1FEF4D307966B8F@vamail01.thexchange.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Clustered file systems is the first/best example that
comes to mind. Host A and Host B can both request from diskfarm, eg.
-----Original Message-----
From: Bruce Momjian [mailto:pgman(at)candle(dot)pha(dot)pa(dot)us]
Sent: Tuesday, April 19, 2005 12:10 PM
To: Mohan, Ross
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: [PERFORM] How to improve db performance with $7K?
Mohan, Ross wrote:
> The only part I am pretty sure about is that real-world experience
> shows SCSI is better for a mixed I/O environment. Not sure why,
> exactly, but the command queueing obviously helps, and I am not sure
> what else does.
>
> || TCQ is the secret sauce, no doubt. I think NCQ (the SATA version
> || of per se drive request reordering)
> should go a looong way (but not all the way) toward making SATA 'enterprise acceptable'. Multiple
> initiators (e.g. more than one host being able to talk to a drive) is a biggie, too. AFAIK only SCSI
> drives/controllers do that for now.
What is 'multiple initiators' used for in the real world?
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-04-19 16:16:01 | Re: How to improve db performance with $7K? |
| Previous Message | Bruce Momjian | 2005-04-19 16:10:22 | Re: How to improve db performance with $7K? |