php.ini file and Page Loading Speed has some relationship as the process are delayed to run by WordPress by default. This is for Rackspace Cloud Sites and Cloud Servers. It can seriously affect the SEO – simply your Sitemap will not be generated in real time, in case you have lot of posts like this website. Secondly, actually the optimized backend only works after using some specific tricks for Rackspace Cloud Sites. There are many users who complains of relatively slower loading speed on Rackspace Cloud Sites, actually, you are not using the optimal settings. Rackspace has no obligation to make your WordPress faster. The page speed experts are usually not used with Rackspace Cloud Sites. So, you need to digg a bit. This website loads within 3.2 seconds without using Rackspace Cloud Files. As this is not very busy website, we do not opt for a complex setup. Knowing less has advantages but knowing more has problems! Just do these tricks and you will understand the practical fact – php.ini file and Page Loading Speed has some relationship. You need not to know theory.
php.ini file and Page Loading Speed : Older Helpful Posts
Read our older article named Rackspace Cloud Sites php.ini details and you will get a custom great script to grab all the needed info. Basically Rackspace do not set any limit for Rackspace Cloud Sites php.ini file. This is done for running PHP applications which demands huge RAM. This is an advantage. But we suggest to add a limit via .htaccess in this way :
|
1 |
php_value memory_limit 1024M |
Why not read this article on Making WordPress to Load Faster on Rackspace Cloud Sites, there are more tricks. And yes, these tricks solves WordPress specific issues like 500 Internal Server Error. In LAMP server with PHP-MySQL application, honestly; 500 ISE is a shame for the software developers. Always check the .htaccess first in case of 500 ISE on LAMP server – this is rule of thumb.
---
php.ini file and Page Loading Speed for Rackspace Cloud Sites
We limited the PHP memory limit via .htaccess to prevent execution of malwares. At least a limit is required to understand the thing is running behind. With unlimited php.ini memory limit, you’ll never understand something might happening and eating 8 GB memory. WordPress needs to add to lines in two files to increase the PHP memory limit. Basically WordPress is not very nicely clean coded software intended to run on a scalable cloud platform, it somehow falls back to 32 MB if we do not add these lines. Probably the logics are incorrect to make it feel as if Cloud Sites is a $3.00 shared server from once very popular shared server with dinosaur logo. Now different ‘colored’ web hosts are there. Honestly, except Rackspace, Amazon, HP cloud; there is no good backend. Media Template has been history. In case of Cloud Server, quite obviously, you will find the line in php.ini file and increase it to not more than 50% of your total physical (we intend to say, the instance’s RAM, actually that is virtual) memory. In case of managed cloud server, you need not to think, the Rackspace guys are real UNIX experts. Do not override their settings. You can point to this article if needed. Rackspace Managed will not cover management of WordPress.
So, the first file is wp-config.php, everyone knows it, add this line :
|
1 |
define('WP_MEMORY_LIMIT', '1024M'); |
Now, go to wp-admin folder and create a file, name it – php.ini and paste this line :
|
1 2 3 |
memory_limit = 1024M upload_max_filesize = 100M post_max_size = 100M |
Now, go to wp-includes folder and you will find a file named cache.php, paste this line :
|
1 |
ini_set("memory_limit","1024M"); |
Value of all should be the same. 1024 MB is practical minimum value to get the advantages of what you are paying for. You will see the speed of backend. By the way, there are other files like install.php file, upgrade.php files; you can add the above lines to make individual process faster. We use 8 GB settings for very resource intensive WordPress websites. It is not that, you will increase as much as you wish, you should tailor it for the best performance with least value. If some plugins are throwing errors like Fatal Error : This and That, again this trick might work. Keep the line high above, so that it semantically works. If you add at the last line, you might get partial benefit.
