My take on this:

You didn't mention if this was a write intensive or read intensive clustered application.. For a read intensive cluster app (such as a search engine, maybe), small localized dbs might be just the trick..

I've done a similar thing, although that was because the client couldn't afford the Oracle licensing fees for a big machine.. put in small local mysql databases on each cluster machine, and then updated through cron every night..

Another somewhat unrelated solution to this is the venerable Squid, working in reverse proxy (httpd acceleration) mode.. again, in a read-intensive environment, serving cached content is far far more effective than multiple servers..

For a write intensive environment though, I might think about partitioning the tables after a careful analysis of the write patterns.. ie: the table x and table y get most of the writes, so put them on separate HDs, or even separate DB servers... My opinion though, NFS is probably not such a good idea if you really want good write performance.. haven't really seen stunningly fast NFS drives (of course, I'm sure I haven't seen really good NFS configs, so this hardly counts)
HTH

In reply to Re: database pooling by tinman
in thread database pooling by chorg

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.