How much will mounting wp-content on a separate NFS server impact performance?

I’m thinking of using multiple web servers with a load balancer in a big WP install. The database will be on a separate server and that’s the easy part. Trickier is files in blogs.dir, and to a lesser extent, the themes and plugins folders.

So I plan to use a separate NFS server, either for all of wp_content or just for blogs.dir. But I’m worried about the performance impact of having these files available over the local network.

If you have done this I would love to hear your thoughts on…

  • Is it wise to share all of wp-content in this way? If not, how about just blogs.dir?
  • How much of a performance trade-off was it?
  • Do you have any suggestions based on your experience?

Thanks.

1 Answer
1

It would depend on the speed of the NFS and the speed of the local network. If your using an object cache like APC the plugins and theme file folders will not be effected because they will be loaded in memory.

A better solution would be to use a CDN or even create your own CDN using a lightweight static file server like Nginx for blogs.dir. W3 Total Cache has built in transparent content delivery network (CDN) integration with Media Library, theme files and WordPress static files.

If you do decide on an NFS there are steps you can take to optimize the performance like the use of NonVolatile RAM, mounting the file system as RAID 0 and making sure you are using UDP instead of TCP.

Leave a Comment