[support] recommended upper limit for memory_limit

Joel Willers joel.willers at sigler.com
Wed Apr 27 16:52:08 UTC 2011


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 at drupal.org [mailto:support-bounces at drupal.org] On Behalf Of Benjamin Jacob
Sent: Wednesday, April 27, 2011 11:28 AM
To: support at 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 at gmail.com> wrote:

> From: Jarry <mr.jarry at gmail.com>
> Subject: Re: [support] recommended upper limit for memory_limit
> To: support at 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/ ]


More information about the support mailing list