Pros & Cons: Multi-DBs for Multisite

  • I’m new to WordPress, and I’ve just successfully installed & configured Multisite, W3 Total Cache, and Domain Mapping on my Nginx VPS. I’m a member of a team of developers, and we’re creating a site that will eventually generate thousands of other sites.

    I’ve heard some arguments that say separate DBs is counter-productive for a multisite network, and others that say that separate DBs is essential.

    On each side, security and performance concerns are raised, amongst others.

    In a pros and cons fashion, and based on our expected volume, can someone explain the pros & cons of using multiple databases and the pros & cons of a single scaled database?

    And I suppose my ultimate question is, what is the recommended method for a large multisite network?

    Please reference any helpful plugins or tutorials for either method.

    Thank You

Viewing 2 replies - 1 through 2 (of 2 total)

  • MultiDB is for cases when you have a DB large enough that it cannot be used on single-server AND/OR it is getting so many hits that a single machine (of any configuration) won’t be able to handle.

    I will suggest adding more RAM/CPUs first. If you reach a point where you cannot add more RAM/CPUs, you will need to use multiple DB. You can then use https://codex.www.ads-software.com/HyperDB (which is used by WordPress.com)

    Thread Starter s.fox

    (@saahirfoux)

    I’m not personally aware of any hard limits on RAM/CPU, at the moment. In fact we’ve added quite a bit so far. Hyper DB does look like a plugin we will investigate. Thanks for the reference, rahul286.

    If anyone else has any further thoughts or comments on this subject, I would welcome them.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Pros & Cons: Multi-DBs for Multisite’ is closed to new replies.