WordPress Scalability – One Instance or Several?

My company is currently outsourcing development of 170 WordPress sites and I recently learned that they are developing all 170 in one instance of WordPress. I am not a WordPress expert, but have seen scalability problems with other CMS products in the past where 50 or so sites in one instance experienced major performance issues over time as the site content and traffic grew. As I said, I am far from a WordPress expert, so I thought I would reach out to the community on this one. Is this a potential problem? Or does WordPress scale well when used this way?

Related posts

Leave a Reply

1 comment

  1. It is very possible to scale WordPress to support multiple sites. WordPress.com, for example, has over 13 million. The trick, when it comes to performance, is to:

    1. Make sure your server can handle it
      If you’re on a shared hosting system, upgrade to a dedicated server (or many). If you’re running 170 blogs, you should have already done this.
    2. Use caching
      Every time a page is viewed, WordPress will go back to the database to re-build the page dynamically. If you have a lot of traffic, this can be very bad for performance (i.e. a lot of sites with a little bit of traffic = one site with a lot of traffic).
    3. Use multiple databases
      Just like you want to try to split your files across multiple servers to ease the load on one system, you want to spread your database system out as well. There are several ways to do this … try Googling for one or two.

    Additional Resources: