recommended upper limit for memory_limit
Hi All, On my website, all pages run fine except for one page where I get the error : 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. I am not too happy about increasing this to 512 M. Is there any way to debug why it's taking so much memory? This is a view of a list of nodes (with paging on). The max number of nodes for this node type wouldnt be more than 200 or so. I am using a shared host (greengeeks) ANy pointers? cheers - Ben
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.
Yeah.. i have similar doubts too. Am no PHP expert, so would you know how n where do i start debugging from? Am using all released modules/views, etc. Also, if a query results 1000s of results, will that cause any issues w.r.t. memory usage/ requirements? cheers - Ben --- On Wed, 4/27/11, Jarry <mr.jarry@gmail.com> wrote:
From: Jarry <mr.jarry@gmail.com> Subject: Re: [support] recommended upper limit for memory_limit To: support@drupal.org Date: Wednesday, April 27, 2011, 4:19 PM 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/ ]
I'd guess that you have error logs somewhere on your server. I'd check those. Or access logs, so you can see what pages are being accessed. Firebug has utilities for telling what items took the longest, so that might help. Sadly, it could be in many places, so you might have to use Devel, which I am just really beginning to use and understand. Basically, it breaks the page down for you and tells you what .tpl.php files are being used, for example. Good luck. It can be tough to find the source of the issue. Joel -----Original Message----- From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Benjamin Jacob Sent: Wednesday, April 27, 2011 11:28 AM To: support@drupal.org Subject: Re: [support] recommended upper limit for memory_limit Yeah.. i have similar doubts too. Am no PHP expert, so would you know how n where do i start debugging from? Am using all released modules/views, etc. Also, if a query results 1000s of results, will that cause any issues w.r.t. memory usage/ requirements? cheers - Ben --- On Wed, 4/27/11, Jarry <mr.jarry@gmail.com> wrote:
From: Jarry <mr.jarry@gmail.com> Subject: Re: [support] recommended upper limit for memory_limit To: support@drupal.org Date: Wednesday, April 27, 2011, 4:19 PM 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/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
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/ ]
sounds interesting. i will expt with this on the offline copy. --- On Wed, 4/27/11, Nicolas Tostin <nicolast@logis.com.mx> wrote:
From: Nicolas Tostin <nicolast@logis.com.mx> Subject: Re: [support] recommended upper limit for memory_limit To: support@drupal.org Date: Wednesday, April 27, 2011, 9:17 PM 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/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
This issues has been resolved. The particular view which was showing up this error, was a view of node type C which had 1..n references of its own type (C). The thing that must have caused this bloat must be because of the unnecsary fields I was loading in the teasers used in the views. In the "Display" section of the content type, in particular, I was including gmaps, references to other 'C' type nodes. I excluded these in the teaser view and voila am back to 128 MB now!! I should relook at all my other content types to ensure unnecesary fields are not loaded for teaser views. cheers - Ben --- On Thu, 4/28/11, Benjamin Jacob <ben4asterisk@yahoo.com> wrote:
From: Benjamin Jacob <ben4asterisk@yahoo.com> Subject: Re: [support] recommended upper limit for memory_limit To: support@drupal.org Date: Thursday, April 28, 2011, 3:08 AM
sounds interesting. i will expt with this on the offline copy.
--- On Wed, 4/27/11, Nicolas Tostin <nicolast@logis.com.mx> wrote:
From: Nicolas Tostin <nicolast@logis.com.mx> Subject: Re: [support] recommended upper limit for memory_limit To: support@drupal.org Date: Wednesday, April 27, 2011, 9:17 PM 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/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
participants (4)
-
Benjamin Jacob -
Jarry -
Joel Willers -
Nicolas Tostin