[support] Resolved - Re: recommended upper limit for memory_limit

[Benjamin Jacob]

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 at yahoo.com> wrote:

> From: Benjamin Jacob <ben4asterisk at yahoo.com>
> Subject: Re: [support] recommended upper limit for memory_limit
> To: support at 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 at logis.com.mx>
> wrote:
> 
> > From: Nicolas Tostin <nicolast at logis.com.mx>
> > Subject: Re: [support] recommended upper limit for
> memory_limit
> > To: support at 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-and-modules.html
> > 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 at gmail.com>
> > To: <support at 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/ ]
>