Drupal Association members fund grants that make connections all over the world.
That indicates that Drupal needed more memory than PHP was allowed to give it.
Where is my php.ini file in Drupal to see my memory limit? - Every system is different. To see your php configuration, create a new php file in your sites root directory and name it "myinfo.php". Inside this newly created blank php file, simply type
<?php phpinfo(); ?> then browse to that file in your web browser by going to http://yoursite.com/myinfo.php
Now you can see where the original php.ini file is as well as other information about your config such as memory_limit.
- For SHARED HOSTING - complete the steps below, creating a php.ini file and putting it in the Drupal root. Copy the entire contents of the original php.ini file and paste them into the new php.ini file you've made in your Drupal root. Now change the memory_limit directive to say 128M.
Memory increase to 128M:
(This has worked every-time; and used to always work for D6 as well)
Create a new file php.ini, and add the code...
php_value memory_limit = "128M"
and put that file in your Drupal 7 (or D6) root folder.
For step-by-step details, see comment below...
Drupal 7 "Fatal error: Allowed memory size of ...".
- For step-by-step details, see comment below...
If you need more than 128M:
Add the line
to your [Drupal 7 root]/sites/default/settings.php file.
I have yet to need this much memory, but I did achieve
a memory increase to 512M using this slightly more complicated
process that involved temporarily changing the permission level
for that file.
- For step-by-step details see the comment below Drupal 7 memory increase to more than 128M.
memory_limit = 32Mto your server's main php.ini file (recommended, if you have access)
memory_limit = 32Mto a php.ini file in the Drupal root
ini_set('memory_limit', '32M');in your sites/default/settings.php file
php_value memory_limit 32Min your .htaccess file in the Drupal root
How to make a shared server refresh and use this new php file - Go to your host and open your cpanel account. Now look for a section that says "PHP Processes"...Open this section, and click "Kill Processes". This will refresh apache and pick up your new php.ini file on a shared hosting account.
End Drupal 7
Increase PHP memory limit
Increase PHP's memory limit, e.g. to increase it to 32M you could try adding:
On most hosts not all of the above methods will work, and some shared hosts will not allow any modification of your capacity at all. Slightly more instructions on increasing PHP memory on your server in the installation guide.
Depending on the amount of modules you have enabled and their 'impact' on the site you may need to increase the memory_limit even more (sometimes to 32 MB or more). Image processing often takes a lot of memory, as can working with any large files. Experiment with what memory value works for your needs.
Clearly, if your error was
memory size of 16777216 bytes exhausted (16M) in the first place, then you are going to have to be bumping the limit up even higher than that. Do the binary thing and double it to 32M.
You may need to restart your server before the php.ini settings take effect.
Note: Do not just set an arbitrarily high number just to avoid this potential problem - it may limit your ability to have multiple simultaneous connections run efficiently, and simultaneous connections are important on web servers.
Reducing Memory Usage
There is no way to know how many or what combination of modules will put any one site over their memory limit. Every module uses a different amount of memory. Core requires memory by itself and requirements for core alone should be understood. see: http://drupal.org/requirements
A frequent example of this error occurs when too much content is retrieved in a single request. This could include using node_load() on a large number of nodes, loading an entire file into a variable (rather than iterating over the file), or creating a large number of dynamic elements on a single page, such as multiple Views blocks or Panels.
1. Views (can) use a lot of memory
Some Views (and Panels and CTools and everything merlinofchaos touches with his mighty, mighty fingers), but it's possible to create configurations with multiple relationships that use a lot of memory. If you disable your Views and the memory issue goes away, it's likely a badly-constructed View causing the issue.
What to do if it is a View, and you really need that View to work? Try putting it into code (Via Bulk Exporter or Features; see below. I've hand-coded Views-like functionality in order to improve performance with very little success) for a start. Another thought is to redo the View a different way -- if ultimately what you're getting at is taxonomy terms, make sure the type of View is a Taxonomy View when creating it; don't create a Content View that uses relationships to get at taxonomy terms.
Could also be worth mentioning here that Panels also supposedly uses a lot of memory -- I haven't really benchmarked it so can't confirm this.
2. Moving stuff from database into code is a very good practice
It took me several Drupal sites to realize this, but keeping everything that's created via a UI in the database (Views and Panels configurations especially) is a Drupal worst practice. Why? It increases load on the database and cannot be version controlled. The first point is particularly problematic in terms of memory usage -- instead of just loading the content from the View from database, the site must also load the view components itself. This is exacerbated by how Drupal uses tables: by abstracting everything to the nth degree, each bit of Drupal's functionality uses a new table, resulting in some requests joining a bajillion tables together. This gives Computer Science people hernias (caveat: link is silly), but can't really be avoided with a piece of software as modular and user-friendly as Drupal is.
The solution? Use Bulk Exporter (Included with CTools) or Features to package up bits of code currently residing in the database as module code.
3. Themes can also eat memory
Does your theme have a lot of template files (I.e., files in themename/templates/)? If so, memory is consumed each time one of those files is loaded. If you're creating templates specifically to suppress bits of Drupal from being displayed, try either:
- Changing permissions so that bit doesn't show up for specific non-admin user roles.
- Using CSS to hide elements.
The first choice is obviously what you want to do for stuff affecting security -- you don't want to use CSS to hide an "edit" button for certain users, only to have them then unhide it via Firebug or whatever.
4. Don't go overboard on contrib modules
While sometimes a site needs a lot of contrib modules, don't go overboard. Each enabled (note: enabled. Disabled modules don't use any memory) module uses memory. This is a bit obvious, but worth noting regardless.
5. The VPS is (sometimes) a lie
In my experience, some unscrupulous hosting companies love trying to push Drupal sites to VPS servers -- they're more expensive and it frees up shared hosting space for ever-more WordPress websites. The situation is worsened by the fact that webhosts often don't advertise (Or even willingly tell you if asked) what the upper memory limit is for shared hosting.
Alas, often if a site isn't under heavy traffic and is still crashing, the issue likely has something more to do with Drupal's configuration than anything else. Pushing a user to VPS just muddies the waters and adds more variables to deal with (Is it the webserver config? PHP config? VPS guest config? VPS host config, even?).
6. When all else fails, clone to localhost and beat it with a stick
This is a big reason why people use the dev-staging-production methodology with version control -- when all else fails, you can do a DB dump, git clone the site to a local testing server and then royally mess up the site on the testing server without worrying about actually breaking anything on the production server.
For memory issues, this generally means disabling modules one by one until the one causing the issue is exposed. It can also point to webhost-related issues -- if the site runs perfectly fine on a local install with memory set to something reasonable like 128MB, then you know your webhost is on crack.