Hi,
I am having a discussion with my friend Derrick here over the minimum requirements for Drupal...
He is reducing the amount of memory drupal is using and is not happy about this error message as he thinks it is too much for a clean install.
Fatal error: Allowed memory size of 262144 bytes exhausted (tried to allocate 30720 bytes) in /XXXXXX/ includes/bootstrap.inc on line 254
In the .htaccess file we have set the
php_value_memory_limit to 32m
Reading the drupal site, a guy said that 32m is not equal to 32mb, but we don't think this is true.
According to drupal 16m is the minimum although 32m is recommend.
So as we have turned all modules off, we are expecting a minimum install of 16m
To get drupal working we bumped up to 64m
His main concern is that we have no extra modules or anything and so it is strange that drupal is asking for over 32mb.
Does anyone know why this might be?
Or gives us some direction to search in?
Thanks.
Comments
could also be a problem
could also be a problem beetween PHP and MySQL.
look at the variables of PHP ("max_allowed_package" and the suhosin limits)
also look at the mysql tables. The Session table could have an overlapping.
That value seems reasonable
That value seems reasonable to me for a no-module install. I find that while some admin pages will use considerably more resources, your average user-visible page with a lot of modules and all the caching enabled will consume somewhere in the range of 30MB. Also I'm not sure if various PHP/PECL/etc. extensions contribute to that value.
--
Dave Hansen-Lange
Director of Technical Strategy, Advomatic.com
Pronouns: he/him/his
I'm with dalin on wondering
I'm with dalin on wondering about plugins (especially xdebug, which can be a hog).
Also, the admin/build/modules page does a lot of work scanning through the modules directory and so disabled modules still have an effect on this page. As a result this page tends to be the most memory hungry in my experience. Generally, if you raise the memory limit until this page passes everything else will load (your mileage may vary).
taxonomy also
A lot of taxonomy terms can cause a high memory requirement as there are several places in the admin where they all get loaded into a select.
Thanks
Thanks everyone...
We were testing only the index page,logged out, all modules off except core and menu from a clean install.
We can look at the extensions and php max packet though.
downside of too much?
what is the disadvantage of using too much? say 96mb?
dashaver
There is no "too much" really
There is no "too much" really as the PHP memory limit just limits the memory available to each single script and is used to prevent the system from going down because of some malfunctional or evil script eating up all the memory.
You can even switch the limit off by setting it to -1 but instead you'd rather go with some higher value which even in a worst case scenario would make sure your machine doesn't run out of ram.
If user-facing pages are
If user-facing pages are consuming a lot of memory then you will have a low capacity to serve simultaneous users. But it's not an issue if user-facing pages consume a small amount of memory, and just the odd admin page requires 96MB.
--
Dave Hansen-Lange
Director of Technical Strategy, Advomatic.com
Pronouns: he/him/his
Derrick says...
So I posed this Derrick and he says;
A high memory limit is not really an issue. It's just if a script is using a lot of memory (which is allowed by a high memory limit), then if you have many people running the same page then a lot of server resources are been used. Therefore the web site gets slow.
If a server has 2000 MB and a web page uses 100MB a page view (Allowed by a high memory limit) then if 20 people view a page at the same time (not sure how likely that is) the server will try to use 2000MB
The last post explains the issue http://groups.drupal.org/node/42430#comment-117502
Since this was a front end view and not an admin. That's my worry.
The lower memory used the better. But as you said there are caching modules etc.. to improve performance
http://loadstorm.com/2009/load-testing-drupal-anonymous-users talks a bit about it improving performance.
I would just like a clean install to use the 16MB - 32MB it says it needs then increase the limit as we add modules.
------ So that's his problem with the ram hit on the bootstrapping.
The high memory limit allows a lot of people to run big scripts.
Then there is a preference to be allowed the clean install which is supposed to be 16mb -32mb but seems it isn't.