So I have a drupal 5.x site set up with 1600 nodes, 10 users, a custom theme, and lots of modules.
I just finished setting up a support part for the site where the client is going to be adding an invoice for all the products he sells. He has roughly 5000 buyers and each buyer buys around 2-5 products minimal from him a year.
So lets say I'll be adding roughly 25,000 extra nodes a year to the site for the support section.
In 5-10 years that could reach 250,000 nodes. Is this a lot? Would this slow down my main section on the website?
My first question is: Should I be creating a separate database for this support section of the website?
Our current database is 35,693 KB.
My second question is: Is creating this new database worth doing? Will it effect the performance?
My third question: How would I go about doing this?
Our website is hosted on a dedicated server. I'm not sure of the specs but I can find out if required.
Thanks for your time / help,
Justin
Comments
One of my site I started 6
One of my site I started 6 months ago have nearly 100,000 nodes, and its still fast on a dedicated server (e! Science News); of course, your queries need to be optimized, im pretty sure an unoptimized query doing a full scan of a table with multiple joins on the front page could bring it down!
Also, in 5-10 years, dedicated servers will be more powerful for cheaper, with more RAM, etc
I really wouldn't worry about 25000 nodes a year. Drupal.org is growing faster i'm pretty sure!
I wouldn't go making extra
I wouldn't go making extra work for yourself by splitting off the database just because it might be faster. I don't think you would gain very much and it could make your life a lot harder down the road. If you're worried about how the site will perform, why not benchmark it? There are scripts that can automatically add 100k nodes. Then you can simulate it on a dev server and see where the pain points are.
Also 35,693 KB is not a very large database. My (multi-site) Drupal database is over 1 GB.