Re: Recommended Hardware Configurations
On 12/17/06, Mike Duffy <[EMAIL PROTECTED]> wrote: I am sure this question has probably been asked in this group before, but I would like to get an updated answer. If you were building your own boxes to run clustered MySQL servers, how would you configure the boxes? (This would of course be for an enterprise level database system.) I am looking for an optimal solution that balances cost and performance; and yes, I realize that is a very subjective standard. I once knew someone who was too cheap to buy a computer case, so he mounted a computer motherboard on a piece of plywood and used it. I don't recommend plywood, but for a cluster you may be able to stack cheap motherboards, power supplies, disk drives, and fans in a single larger metal enclosure (depends on how handy you are at this kind of fab in general). This is at the EXTREME low end of price. Even with 5G of RAM on each one, you may be able to average $600 - $700 per motherboard, all costs included. I'd start with a half-height rack enclosure, and see if you can develop a regular pattern to "repeat" within. Enterprise-grade servers are EXPENSIVE.
Re: Recommended Hardware Configurations
On Sunday 17 December 2006 13:20, Mike Duffy wrote: > My intuitive judgment is that we would be better having several smaller > systems in a cluster rather than one huge powerful system and that we would > be better off building rather than than buying. If you think I am wrong on > either of these points, please share your thoughts and send a link to a > recommended system. Well, this gets tricky. If you take a look at: http://www.mysql.com/products/database/cluster/faq.html you'll notice very high requirements for each cluster node. This is mainly due to the fact that mysql clustering does not support filesystem writes (right now at least, I've heard that's supported later). That said, the database has to be stored into memory. If you have a 10 node cluster supporting a 5 gig database, that means all 10 boxes have to have 5+gigs of memory, otherwise it won't work. A single system is a bit easier to manage, but you have to be extra particular about your failsafes, as you've now centralized the point of failure to 1 machine. On the other hand, should your database grow, you just feed it more ram and be done with it, or upgrade the server later on (if you get a really large db). -- Chris White PHP Programmer Interfuel -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Recommended Hardware Configurations
I am sure this question has probably been asked in this group before, but I would like to get an updated answer. If you were building your own boxes to run clustered MySQL servers, how would you configure the boxes? (This would of course be for an enterprise level database system.) I am looking for an optimal solution that balances cost and performance; and yes, I realize that is a very subjective standard. My intuitive judgment is that we would be better having several smaller systems in a cluster rather than one huge powerful system and that we would be better off building rather than than buying. If you think I am wrong on either of these points, please share your thoughts and send a link to a recommended system. Sincerely, Mike __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
