WordPress is growing and growing, with the growing of WordPress the demand of memory is also growing. The standard use is WordPress 32MByte (see settings.php ), which is not even provided by every hoster today. This is a problem – therefore: Lovely Hoster, give users more memory!
But also to use the memory, it requires a small syntax extension in the configuration of WordPress.
To have a quick overview about the demand: Use the Plugin for WordPress WP-Memory-Usage by Alex Rabe …
… or the more extensive version of an analysis with the Plugin WordPress System Health by Heiko Rabe.
More Information
Thus, it provides the analysis of blogs and a quick way to see the problems at a customers blog or project of your own. This WordPress Plugin Health System will not only provide information on the status of WordPress, but will also provide information on important configuration settings, supply information on the state of the database and also the tables and information about PHP. In each mode you can add various details, which provide a lot of information to the WordPress experts about the system without the need to investigate the individual Settings, the PHP and the database information.
More Memory
It is recommended when working with WordPress to increase memory, as long the host permits. This requires the expansion of wp-config.php; the best way is to do it in steps in order to check the possibilities of the host.
// more memory
define('WP_MEMORY_LIMIT', '64M');
// even more memory
define('WP_MEMORY_LIMIT', '96M');
// a good deal more memory ;-)
define('WP_MEMORY_LIMIT', '128M');
Will you get a white page as return, then it was too much and it goes back down to 32 MByte. Good luck.
Comments
15 responses to “More Memory For WordPress – More Information About WordPress”
Will this help running wordpress faster i guess, since lots of people cant increase memory on shared hosts
Just curious, when you say it’s recommended to run WP with more memory, recommended by whom? What are the specific benefits? Any benchmarks?
Naturally, it sounds like a good idea, just wondering what the science is behind it.
[…] trata de un simple Widget, desarrollado por Alex Rabe, que nos vá mostrando con una gráfica de colores el nivel de memoria consumida sobre el máximo de memoria establecida para WordPress. Muy útil para los que tienen problemas de […]
WordPress won’t run faster with more memory, it will just run. Which beats the alternative where it doesn’t run at all or runs and breaks in the middle.
Jacob: Sounds about right. Important to understand the distinction, because if you’re running wp-super-cache, for example, the returns on this will be minimal. Good to know none the less.
I really would like to know the benefits of this more memory? How does it really help WordPress by increasing the memory limit in this manner.
Perfect, Ive been wondering how to adjust this for awhile. Thanks!
I’m starting to think that WordPress has choose the “Windows” path: more memory and resources used for a very small increase in (often unrequested) new functions.
Each release is more nice to play with but as a pro blogegr I think the latest releases require more time to create a post and upload the images…
Beside closing some security oles, what are the big benefits of the latest releases?!
Frankie
ops, I forgot a small tip:
to know how much memory is allocated by the host is possible to uset the plugin WP Security Scan:
http://wordpress.org/extend/plugins/wp-security-scan/
Oh, thank you, it was so easy and I was looking for it for so long, I thought I had to ask to my host but i just changed the numbers and it worked fine.
@Ajay: There are many aspects where increasing the memory is a must. For example I have been running one blog for six years now with more than 3000 posts, the tags alone in that many posts are more than 50mb worth of DB space. The longer we blog the more memory it will take to run even semi-popular blogs with any sort of efficiency.
@Frankie: it isn’t so much a windows approach, though some plugins are definitely taking that approach. One of the biggest time wasters when it comes to making a post is the autosave function. There are several ways to turn this off or avoid its excessive use. I have tried several DB management plugins that will disable the feature, which is my preference. The second way to avoid it is to post with a client such as windows live writer or scribefire.
Interestingly, post my comment, I had to implement this when I moved to shared hosting.
Surprisingly it worked and I now run pages at 64MB, however, it would have been great if I could only choose to run the admin area with this much memory
[…] I stumbled across this post about how much memory WordPress uses now. Apparently, a "regular" WordPress blog installation now uses 32 MB of RAM. The most […]
In my wordpress installation i run pages at 96MB 🙂
It does not work!