Rackspace Cloud Database is an excellent product for WordPress which not only can increase the performance but also secures the installation. Rackspace Cloud Database is intended for fully advanced UNIX users if unmanaged plan is used or if you are using managed level, you need not to think about anything. We are telling you why this Rackspace Cloud Database is better option over having 2 MySQL master slave servers.
Rackspace Cloud Database for WordPress Usage Guide
Right now, you have installed WordPress on Rackspace Cloud Server (Ubuntu 14.04 PVHVM) following our one server guide, right? We wrote the guide in a way, so that you actually can upgrade or rather have options to scale up. Increasing RAM is quite difficult matter, most importantly if you want to keep the IP same. You can test it and throw away, it will cost few cents to add Rackspace Cloud Database for WordPress Installation using our guide or official guides. If you follow other’s guide or punch it with ours, we can not give any warranty whether it will seamlessly work.
It is Database as a Service – why wrote nearly 2 years back why it is effective. This is new OpenStack based Database as a Service. We have one server, full setup to run WordPress, right? Now point towards Databases and proceed to create an one GB Database. Stop, do not create, there are tricks, keep the page in that way!
You can scale down later in working condition. SSH to our existing full all-in-one server. You need to install the MySQL Client :
1 | sudo apt-get install mysql-client |
Fully follow this guide :
1 | http://www.rackspace.com/knowledge_center/article/importing-data-to-cloud-databases |
(do not read the comments there, they are failed Gurus trying DIY method)
OK, we are writing the commands here in case in future they change or remove it for technical reason. On our existing server, first make the dump (you will login as root) :
1 | mysqldump -u username -p database_name > database_name.sql |
or the above command, you will use the credentials for your existing server’s database. Now, open the half completed step to create Cloud Database. Use the exactly same Database username, Database password to create a fresh MySQL Cloud Database – wow. Wow because its great idea. First export the database to that newly created database on Cloud Database (you are on SSH on our formulated server).
Advertisement---
1 | mysql -h 31blah2d.rackspaceclouddb.com -u username -p database_name < database_name.sql |
That 31blah2d.rackspaceclouddb.com part is FQDN and will be different for you. It is exactly like Rackspace Cloud Sites. Now edit the wp-config.php file :
1 | nano /var/www/html/wp-config.php |
just change the database name to that longer FQDN (from localhost or localhost’s IP). Save it. Stop MySQL service :
1 | sudo service mysql stop |
Check if your WordPress is loading or not! It will load ! Its so easy. In case you want to SSH to the server, you need to add a load balancer temporarily to that MySQL instance. If you want to do more fun, BIND that IP with your this all-in-one server’s my.cnf file. You’ll get the PHPMyAdmin!
Why Rackspace Cloud Database for WordPress is Good Option to Think
They have excellent API based monitoring tool, it is named Cloud Intelligence :
Its an optimized database, the tools are free. Just think, 98% CPU consumption with 1 GB instance! Its great tool to find why, which process is eating memory. Look, the practical fact is – one server all-in-one setup is actually the best solution for WordPress. It has lot of buggy plugins, itself it is badly coded. Latency definitely increases by few milliseconds when we are using a database of outside – another computer. But as you know, more program a computer will run, more the chance it will have to hang. Hanging for MySQL is MySQL Gone Away Error. People can not hack because it is not accessible via SSH without adding a load balancer or server. You can add multiple databases, but we do not recommend it for WordPress. Right after installation, there will be some sluggishness, it will go away when database will be cached. Do not forget to clear your W3 TC or any database cache after the change.
