Hi, I was wondering if anyone could recommend a database clustering solution for a massive warehouse. Rails/flex being the main front end. Talking a few million rows, with queries that may touch a million rows every few seconds. I was giving some thought to a MySQL clustering project like Sequoia. http://sequoia.continuent.org/HomePage Or possibly just hiring a consulting firm to come in. We''ve done some good size projects, but this will be the biggest we''ve done to date. -- Thanks -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
> Hi, I was wondering if anyone could recommend a database clustering > solution for a massive warehouse. Rails/flex being the main front end. > > Talking a few million rows, with queries that may touch a million rows > every few seconds. > > I was giving some thought to a MySQL clustering project like Sequoia. > http://sequoia.continuent.org/HomePageWe tried continuent a year or two ago and gave up. And our database was small (couple hundred megs). We had three nodes and had problems with a node crashing bringing the other nodes down. With the result being we had to power cycle each of the boxes. We never made it to production. That said, it was about two years ago. Hopefully it''s improved, but I''ve been soured by the experience. Also, that wasn''t sequoia, it was their commercial offering. No idea what difference that makes. In our case we ended up just using a single master with multiple slaves and the mysql_replication_adapter to spread the load. -philip --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
That kind of replication is more than you really want to have on a simple master-master or master-slave replication. Your better off bringing in someone with experience with that scale of DB, and using whatever they recommend to you. Rob Kaufman http://notch8.com On Fri, Mar 14, 2008 at 12:19 PM, Philip Hallstrom <philip-LSG90OXdqQE@public.gmane.org> wrote:> > > Hi, I was wondering if anyone could recommend a database clustering > > solution for a massive warehouse. Rails/flex being the main front end. > > > > Talking a few million rows, with queries that may touch a million rows > > every few seconds. > > > > I was giving some thought to a MySQL clustering project like Sequoia. > > http://sequoia.continuent.org/HomePage > > We tried continuent a year or two ago and gave up. And our database was > small (couple hundred megs). We had three nodes and had problems with a > node crashing bringing the other nodes down. With the result being we had > to power cycle each of the boxes. We never made it to production. > > That said, it was about two years ago. Hopefully it''s improved, but I''ve > been soured by the experience. Also, that wasn''t sequoia, it was their > commercial offering. No idea what difference that makes. > > In our case we ended up just using a single master with multiple slaves > and the mysql_replication_adapter to spread the load. > > -philip > > > >--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---