On Tue, Mar 24, 2009 at 7:32 AM, RobR <[email protected]> wrote: > First, I'm a physicist, not a computer scientist. I need to store 65M > rows now, with a growth rate of ~21M/year whose entries arrive daily.
MySQL can deal with this out-of-the-box without breaking a sweat. I wouldn't worry about partitioning until you actually hit a wall. I think Moore's law is on your team for this project. (Note: you probably don't want indexes on every single column individually. Add compound indexes tuned to your actual queries.) Best, jeremy --~--~---------~--~----~------------~-------~--~----~ 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
