Thanks for the wiki link, will check. But, quite right, we need to maximize the bandwidth utilization of each link in the chain as it were, drives, controller, host slot, more than enough is of no use, who can drink from a fire hose?<br>
<br>We're talking server grade stuff here, no 'home brew' mobos, this is a board of realtors office and they don't want no stinkin down time, in so far as possible/affordable.<br><br><div class="gmail_quote">
On Tue, Jul 28, 2009 at 2:19 PM, Jim Kinney <span dir="ltr"><<a href="mailto:jim.kinney@gmail.com">jim.kinney@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
There are some rather fast pci bus config around but you need serious<br>
mobo data to know for sure. Most home-user pc's are crap with even<br>
multiple pcie sharing a common interconnect.<br>
<br>
For numbers on device bandwidth, see here:<br>
<a href="http://en.wikipedia.org/wiki/List_of_device_bandwidths" target="_blank">http://en.wikipedia.org/wiki/List_of_device_bandwidths</a><br>
<br>
You don't want more devices on a card than the slot it's plugged into<br>
can take :-)<br>
<div><div></div><div class="h5"><br>
On Tue, Jul 28, 2009 at 1:37 PM, Greg Clifton<<a href="mailto:gccfof5@gmail.com">gccfof5@gmail.com</a>> wrote:<br>
> Hi Jim,<br>
><br>
> You do mean PCIe these days, don't you? Being serial point to point data<br>
> xfer resolves the bus contention issue, no? Ain't much in the way of<br>
> multi-PCI bus mobos to be had any more as the migration to PCIe is in full<br>
> swing. I expect PCI will be SO 20th century by Q1 '10.<br>
><br>
> What about a single 12, 16, or 24 drive RAID controller from 3Ware or Areca<br>
> (PCIe x8 native, I believe for both now). I'm sure it is much greater than<br>
> PCI (even PCIX @ 133MHz ~ 800mb/s), but what is the bandwidth on PCIe<br>
> anyways?<br>
><br>
> You are basically talking RAID 10 type configuration, no? Using the entire<br>
> drive vs. short stroking so no complications in prepping a replacement<br>
> drive, good thought.<br>
><br>
> As Richard suggested, customer is interested in some sort of mirrored/load<br>
> balanced/failover setup with 2 systems (if it fits the budget). How to, is<br>
> where I am mostly clueless.<br>
><br>
> Thanks,<br>
> Greg<br>
><br>
> On Tue, Jul 28, 2009 at 12:24 PM, Jim Kinney <<a href="mailto:jim.kinney@gmail.com">jim.kinney@gmail.com</a>> wrote:<br>
>><br>
>> multi-pci bus (not just multi pci _slot_) mobo with several add-on<br>
>> SATA300 cards. Hang fast drives from each card matching the aggregate<br>
>> drive throughput to the bandwidth of the pci bus slot. Make pairs of<br>
>> drives on different cards be mirrors. Join all mirror pairs into a<br>
>> stripped array for speed.<br>
>><br>
>> Use entire drive for each mirror slice so any failure is just a drive<br>
>> replacement. Add extra cooling for the drives.<br>
>><br>
>> On Tue, Jul 28, 2009 at 11:35 AM, Greg Clifton<<a href="mailto:gccfof5@gmail.com">gccfof5@gmail.com</a>> wrote:<br>
>> > Hi Guys,<br>
>> ><br>
>> > I am working on a quote for a board of realtors customer who has ~ 6000<br>
>> > people hitting his database, presumably daily per the info I pasted<br>
>> > below.<br>
>> > He wants fast reads and maximum up time, perhaps mirrored systems. So I<br>
>> > though I would pick you smart guys brains for any suggestions as to the<br>
>> > most<br>
>> > reliable/economical means of achieving his goals. He is thinking in<br>
>> > terms of<br>
>> > some sort of mirror of iSCSI SAN systems.<br>
>> ><br>
>> > Currently we are only using 50G of drive space, I do not see going above<br>
>> > 500G for many years to come. What we need to do is to maximize IO<br>
>> > throughput, primarily read access (95% read, 5% write). We have over<br>
>> > 6,000<br>
>> > people continually accessing 1,132,829 Million (as of today) small (<1M)<br>
>> > files.<br>
>> ><br>
>> > Tkx,<br>
>> > Greg Clifton<br>
>> > Sr. Sales Engineer<br>
>> > CCSI.us<br>
>> > 770-491-1131 x 302<br>
>> ><br>
>> ><br>
>> > _______________________________________________<br>
>> > Ale mailing list<br>
>> > <a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
>> > <a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
>> ><br>
>> ><br>
>><br>
>><br>
>><br>
>> --<br>
>> --<br>
>> James P. Kinney III<br>
>> Actively in pursuit of Life, Liberty and Happiness<br>
>> _______________________________________________<br>
>> Ale mailing list<br>
>> <a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
>> <a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
><br>
><br>
> _______________________________________________<br>
> Ale mailing list<br>
> <a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
> <a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
><br>
><br>
<br>
<br>
<br>
--<br>
--<br>
James P. Kinney III<br>
Actively in pursuit of Life, Liberty and Happiness<br>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
</div></div></blockquote></div><br><input id="gwProxy" type="hidden"><input onclick="jsCall();" id="jsProxy" type="hidden"><div id="refHTML"></div>