2bits has a patch to find out which module consume memory: http://2bits.com/articles/measuring-memory-consumption-by-drupal-bootstrap-a... But the big problem is that module can now load more code depending of the context so I think it's quite difficult to pinpoint the culprit. I am very interested in knowing a good solution for this problem as my site also suffer heavy memory consumption. Good luck. ----- Original Message ----- From: "Jarry" <mr.jarry@gmail.com> To: <support@drupal.org> Sent: Wednesday, April 27, 2011 11:19 AM Subject: Re: [support] recommended upper limit for memory_limit
On 27. 4. 2011 16:34, Benjamin Jacob wrote:
Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to
allocate 7680 bytes) in /home/website/somefile.php
I have used Drupal tweaks and the value is currently set to 256 MB, so obviously the limit's crossed.
Hm, that's strange. I have quite complicated site, with many modules, large database, even blocks with some not very "clean" custom php-scripts, yet my site runs well with standard 128MB. I tried to increase it to 256 or even 512, but did not notice any signifficant difference...
I's suspect that php-script of yours. Maybe it's leaking memory somewhere. I can't imagine a script where 256MB is not enough. Only if it was called in parallel from thousend clients at one time, without caching results...
Jarry -- _______________________________________________________________ This mailbox accepts e-mails only from selected mailing-lists! Everything else is considered to be spam and therefore deleted. -- [ Drupal support list | http://lists.drupal.org/ ]