Kevin C Pirnie

High Performance WordPress and Server – Part I – Server Setup

High Performance WordPress and Server – Part I – Server Setup

I have successfully managed to get under a 1 second load time on my WordPress site, While getting 250 concurrent users over a 1 minute test period.  (Source: & This was done with a combination of items, stemming from the server install up to WordPress theme development.  Here is how I did it, so maybe you can too.

Server Setup

Here we will start from the ground up.  Items you will need: VirtualBox, Ubuntu 16.04 64b Server ISO, Time My virtual machine is setup with 4G of RAM, using 2 CPU’s, with 80G SSD, and a Bridged Networking adapter Boot to the ISO, and start the installation process.  Everything can be setup how you wish, however, I custom partitioned, as well as, only installed the “standard system utilities”, and OpenSSH during the install process. During paritioning (with the size above), make sure to select Manual, and setup the 4 Partitions I layout below Since we are creating a tmp, cache, and swap partition make sure to reserve at least the same amount as you have in RAM, so with my 4G of RAM, I need to reserve at least 12G of disk, however, I am going to reserve 16G because I want my swap partition twice the amount of RAM Now finish up your install process, and let the machine reboot.  Once it boots, login to the machine and drop into a sudo session using sudo -s and let the “fun” begin 🙂 We are going to configure our server to use bash only, setup the default system control, install our software, and configure it… so be prepared to have your time sucked up 😉 Use bash only: dpkg-reconfigure dash Now, we’ll remove apparmor since we’ll be using ufw as our firewall
service apparmor stop
update-rc.d -f apparmor remove
apt-get remove apparmor apparmor-utils
Speaking of firewall, we can set that up now too
ufw allow http
ufw allow https
ufw allow ssh
ufw enable
This will allow only web and ssh connections to the server.   Feel free to allow anything else you deem necessary Now we’ll modify our system controller to allow a ton of connections, allow a ton of files to be open, and mod our networking and swap configuration First run rm -f /etc/sysctl.conf  then nano /etc/sysctl.conf  and paste in the following: After you save the file, run the following to load in the configuration: sysctl -p Now add in the following line to your limits by: nano /etc/security/limits.conf
# add to bottom
* - nofile 16384
* hard nofile 500000
* soft nofile 500000
root hard nofile 500000
root soft nofile 500000
Now we’ll update the server: apt-get update && apt-get -y upgrade && apt-get -y dist-upgrade && apt-get autoclean && apt-get -y autoremove Once again, you will need to reboot. Once you have rebooted, lets forge ahead and install our web/database software:

nGinx & memcached (and a couple extra helpers)

apt-get -y install nginx-full memcached zip lzop


apt-get -y install php7.0-fpm php7.0-curl php7.0-gd php7.0-intl php7.0-mysql php7.0-json php7.0-sqlite3 php7.0-opcache php-memcached php-pear php7.0-mbstring php7.0-cli


apt-get -y install mysql-server
We are done installing! 😀   Now the real fun begins… configuration.  Since I host a multitude of sites on my server, I setup a directory structure like the following for both site configurations and files.  But, you can do what you want…  just remember to change your paths in the config files I post here, otherwise it will not work for you.
  • /hosting
    • /hosting/DOMAINS
      • /hosting/DOMAINS/
        • /hosting/DOMAINS/
        • /hosting/DOMAINS/
    • /hosting/nginx-config
    • /hosting/site-config
I remove the default nginx config otping for my own, so do a: rm -f /etc/nginx/nginx.conf && echo “include /hosting/nginx-config/nginx.conf;” > /etc/nginx/nginx.conf Now download the following and unzip it to your /hosting/nginx-config/ directory: DOWNLOAD HERE You are now ready to setup your first site.  Run this and change the domain to the domain of your need: mkdir -p /hosting/DOMAINS/ && echo “<h1>Hello World</h1>” > /hosting/DOMAINS/ We also need to configure the running of your site through fpm and nginx, copy and paste the following to /hosting/site-config/ make sure to change the paths to fit your needs, as well as the domain.
upstream your-fpm-lb {
	# PHP-FPM - make sure the ports you decide to use are open
        # You should at least have 2 pools available to you.  But really no more than 4 is necessary

# Redirects
server {
	# what we want to redirect
	# where we want to redirect to
	return 301$request_uri; 

server {
	# the document root of your site
	root /hosting/DOMAINS/;
	# the default page for your site
	index index.php;
	# the main fqdn of the site
	# your access log location.  I leave this commented for performance
	#access_log /logs/;
	# your error log location, i only enable critical errors to log - performance
	error_log /logs/ crit;
	# let’s setup the php fpm processor
	location ~ [^/]\.php(/|$) {
		# let’s turn on the keep alive
		fastcgi_keep_conn on;
		# include our default fastcgi configuration: see file for details
		include /hosting/nginx-config/site-fastcgi-common.conf;
		# set to your fpm upstream above
		fastcgi_pass your-fpm-lb;
	# Configure memcached to be usable. See file for details 
	include /hosting/nginx-config/memcache-enabled.conf;
	# Configure caching. See file for details
	include /hosting/nginx-config/yes-cache.conf;
	# Configure no caching. See file for details
	#include /hosting/nginx-config/no-cache.conf;
	# Configure default site settings, Required.  See file for details
	include /hosting/nginx-config/all-sites.conf;
	# Configure gzipping of static resources.  See file for details
	include /hosting/nginx-config/gzip.conf;
	# Configure some extra security for WordPress sites.  See file for details.
	include /hosting/nginx-config/wp-security.conf;
One last bit of configuration.  We need to setup our fpm pools.  Since we configured 4 upstream connections in our site config, we need to configure 4 pools Create a new user for these pools to run under adduser -y example-user Copy and paste the following into 4 files located in /hosting/DOMAINS/
; Start a new pool
; make sure to update the number
; what user should this pool run as
user = example-user
; keep this www-data so nginx can serve the site
group = www-data
; change this to reflect one of the ports in the upstream block of your site config
listen =
; We don’t need to have too high of a task priority
process.priority = 0

; fpm process management
pm = dynamic
pm.max_children = 200
pm.start_servers = 20
pm.min_spare_servers = 20
pm.max_spare_servers = 60
pm.max_requests = 500
We can now start our engines 🙂   Run this command to make sure you haven’t messed up anything 😉 nginx -t  then run the following to restart all of your services to start hosting your site.
/etc/init.d/memcached restart
/etc/init.d/php7.0-fpm restart
/etc/init.d/nginx restart
Now that we have the “basics” out of the way, let’s head into configuring MySQL to handle the loads we are going to place on it.    Copy/Paste the following into your mysqld.conf (usually located at /etc/mysql/mysql.conf.d) For the most part we are now done and ready to start serving up scalable, efficient, and fast loading WordPress websites.  Just the config above alone is not enough to ensure high availability though.  There is alot more work to be done, mostly with theme development. Just like any other web application, proper development goes a long way.  Design as well, if your app’s design isn’t optimized, you will still create a heavy load on the server, that is un-necessary.  Always optimize your images, always set the dimensions when you call them as well.  Make sure you concatenate and minify your css and javascripts where you can, and load them appropriately in your html code.  (css in the head, keep as much javascript at the bottom of your documents as well). That’s it for now, stay tuned for the rest in this series.  And as always…   Happy Coding 🙂  

About the author

Kevin P

22 Years of PC and server maintenance, you can rest assured that I take every measure possible to ensure your computers are running to their peak potentials. I treat them as if they were mine, and I am quite a stickler about keeping my machines up to date and optimized to run as well as they can. If I’m not happy with the way a machine runs, I know my clients would not be, so I take those extra steps to ensure it is secure, safe, and fast.

Wordpress Hosting, Development, ManagementContact Me Now