[resolved] Reasonable # of db tables for our size of Multisite? (11 posts)

  1. davegregg
    Posted 4 years ago #

    Alright, so I have 324 blogs on a single WordPress Multisite installation that we started almost two months ago. Bluehost just contacted me saying that we're close (2,900) to maxing out the number of database tables (3,000) we can use account-wide. We do have a premium account.

    First question: is that number of tables unexpectedly high for the number of blogs we have? Could something be squatting on tables unnecessarily?

    Second question: is there a way to significantly consolidate or otherwise reduce that number of tables down to a number that will allow us to continue to grow? How much time might we have before *needing* to switch to a dedicated server? I know that's a ridiculous question to have to ask; we should just do it, but I don't make the decisions.

    Other information: Despite having so many blogs, we don't have tons of traffic. These blogs are often set up and then left to stagnate.

    Any other suggestions/ideas?

    Any help would be appreciated. Thanks!

  2. That's quite the small limit there. Bluehost's premium accounts are still shared accounts. You could move to a vps. You could split up the db. You could clean out the old blogs.

    You cannot reduce the number of tables per blog. Each blog does have 9 tables.

    324 x 9 = 2916

  3. davegregg
    Posted 4 years ago #

    Okay so I'm not going crazy. We just made a poor decision going with Bluehost. So, what's a good VPS? I've been looking at HyperDB and Multi-DB. But we can't clean out old blogs, unfortunately -- if for no other reason than none of these blogs are currently older than two months. The stagnation comment is the trend I've seen with the blogs we've set up for our clients in the past, utilizing other services. This is the first time we've decided to manage a blogging option ourselves, rather than outsourcing it, as it were. So seeing as we're building 100-200 blogs per month, is VPS going to be a solution that could last us a year or two?

  4. We can't make hosting suggestions (though I suspect Andrea and I both have ad links on our personal sites to hosts we use).

    A good VPS should last you a while. I've heard mixed things about Cloud Hosting, so I'm not sure about that one yet.

  5. and shardb

    that'll spit the dbs up into multiple ones so those 3K tables can be spread across 16 or more dbs. You can use that at your current host to bide some time.

  6. davegregg
    Posted 4 years ago #

    Thanks Andrea & Mika for the help. I don't think splitting up the DB will help until after we move to a VPS or dedicated server, because even if the tables are in multiple DBs, we still can't have any more tables than we already do. Bluehost told me that the 3k table limit is account-wide, not per-database.

    BUT I will need to use a solution like that once I move over to the VPS. Understanding that I don't have a lot of experience with backend stuff, would you suggest SharDB, HyperDB, or Multi-DB for me? As long as I have documentation and maybe support, I think I'll be able to bluff my way through it. I see now that SharDB has a manual now... didn't know that. But just so you know I'm not very experienced with databases.

    Though this is slightly off-topic, do you have a preferred beginner's resource for learning SQL or MySQL?

  7. I'm gonna say shardb cuz I wrote the manual. :P

  8. I'm going with SharDB since I found it easier to implement for only a couple DBs ;)

  9. davegregg
    Posted 4 years ago #

    So am I going to experience an upper limit of tables per database at MediaTemple on a VPS?

  10. Probably not, but you should ask them.

    I've hosted a site with over 600 blogs at a couple different VPS providers.

  11. davegregg
    Posted 4 years ago #

    Cool. Many thanks, Andrea & Mika! You've been such a help to me! I'll mark this topic resolved.

Topic Closed

This topic has been closed to new replies.

About this Topic