Thread

Hi

EE version: 1.6.9
Build: 20100415

My client has reported a white screen on a page on their live site that was previously working fine. After investigating the issue it seems that memory is being exhausted on a reverse_related_entries tag. I’m puzzled by this because the number of entries being found by the tag is no more than 40-50. However, I do have a large number of fields in the exp_weblog_fields table (183 across all weblogs)

Luckily, this issue has already been raised (and a temporary fix posted) in these forums. However, I’m very concerned that this could happen again at some random point in the future when the memory reaches critical mass again.

My question is: why are are these memory issues occurring in a site that only has a relatively modest number of weblog entries in the database (462 across all weblogs). Surely the memory shouldn’t be even remotely taxed in this scenario? What’s going to happen when the number of users goes up? The worst thing is feeling like I’ve got no control over this - the memory could be exhausted at any time and I’ve got no way of knowing. This is somewhat worrying to say the least. I’m really surprised this issue has only recently arisen.

Thanks
Simon

Welcome to the forums, Simon. How much memory do you have in this case?

Hi Ingmar

It’s currently 16 MB, which I know is pretty low (I’m going to get it raised, just to be on the safe side). However, at the moment the site is in pre-launch mode so only 1 or 2 people are using it at any time. So I’d expect memory use to be minimal - hence why I was surprised that we’re already reaching memory limits.

It seems that reverse_related_entries is pretty heavy on the memory. Is this because of the relationship cache that can get quite large?

Thanks
Simon

It’s currently 16 MB, which I know is pretty low

I am afraid that really isn’t a lot, yes. I use usually 4 times that much on my standard setups. 16 MB must be considered the bare minimum these days.

However, at the moment the site is in pre-launch mode so only 1 or 2 people are using it at any time.

That doesn’t matter. The limit applies to individual PHP processes: if there’s something memory intensive like, say relationships or image manipulations it doesn’t matter how few people there are.

It seems that reverse_related_entries is pretty heavy on the memory.

Well, yes. That said I never ran into any problems with it yet using a moderate amount of both channel entries and memory.