[ale] Fault Tolerant High Read Rate System Configuration

[Rev. Johnny Healey]

As a software guy and two things jump out at me:

-if this is a database with a lot of reads and very few writes,
memcache is a godsend.  It requires the app developers to know how to
use it, but, when it can take a lot of load off of the database (if
used wisely).

-if you're looking to store a bunch of small files in a redundant way,
you may want to look at mogilefs.  It stores files redundantly across
a series of machines.  Though, I believe it also requires apps to be
aware of it.

Conveniently, they are both available at the same place: http://www.danga.com/

-Rev. Johnny Healey
President of the Brad Fitzpatrick Fan Club

On Tue, Jul 28, 2009 at 11:35 AM, Greg Clifton<gccfof5 at gmail.com> wrote:
> Hi Guys,
>
> I am working on a quote for a board of realtors customer who has ~ 6000
> people hitting his database, presumably daily per the info I pasted below.
> He wants fast reads and maximum up time, perhaps mirrored systems. So I
> though I would pick you smart guys brains for any suggestions as to the most
> reliable/economical means of achieving his goals. He is thinking in terms of
> some sort of mirror of iSCSI SAN systems.
>
> Currently we are only using 50G of drive space, I do not see going above
> 500G for many years to come. What we need to do is to maximize IO
> throughput, primarily read access (95% read, 5% write). We have over 6,000
> people continually accessing 1,132,829 Million (as of today) small (<1M)
> files.
>
> Tkx,
> Greg Clifton
> Sr. Sales Engineer
> CCSI.us
> 770-491-1131 x 302
>
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale
>
>