[horde] How much memory to set memory_limit to?

[Simon Brereton]

On 29 November 2011 03:30, Michael M Slusarz <slusarz at horde.org> wrote:
> Quoting Simon Brereton <simon.brereton at buongiorno.com>:
>
>> On 25 November 2011 17:21, Michael M Slusarz <slusarz at horde.org> wrote:
>>>
>>> Quoting Simon Brereton <simon.brereton at buongiorno.com>:
>>>
>>>> On 25 November 2011 16:20, Pro Green European
>>>> <pro_green_european at yahoo.com> wrote:
>>>>>
>>>>> Hi.
>>>>>
>>>>> I've set 512M as the default memory_limit value in PHP for my webmail
>>>>> system.
>>>>>
>>>>> How much should I really allocate? I think 512M is quite a lot of
>>>>> memory.
>>>>>
>>>>> I've tried with 384M, but it didn't take long before I started seeing
>>>>> memory exhausted messages in Apache's error log.
>>>>
>>>> This was discussed at length a few weeks ago because of an issue I was
>>>> having.  You should be able to find the thread in the archive.  Some
>>>> were ok with 256, some recommended 512 and some even proposed 1024.
>>>> Currently I'm up to 384, but I can go to 512 if I get more out of
>>>> memory messages.
>>>
>>> And as I previously mentioned, all of these values seem exceedingly high.
>>>  Especially for viewing a message.
>>>
>>> The only possibility of reaching this kind of memory use is by using the
>>> SQL
>>> VFS backend.  This is now highly discouraged - use the filesystem VFS
>>> backend instead.
>>
>> Thanks Michael.  I am indeed using the SQL VFS - I'll switch to the
>> filesystem VFS and see.  However, I'm a little reluctant to do so
>> without a better understanding of what gets placed.  Can you shed some
>> light on that?  Also, I used the SQL VFS because that's what I was
>> using in H3.  If filesystem is recommended for H4, then the drop-down
>> option in the VFS tab should have a (recommended) next to it  (and
>> perhaps a notes as to the reasons why).
>
> It is mentioned in imp/docs/PERFORMANCE.
>
> This is not something that should go into the base configuration file(s) -
> it is a performance issue, not a configuration issue.

That maybe so - but JS caching and CSS caching could also be
performance issues and they have HUGE warnings about what the
recommended option is in the set-up.  Adding (Recommended) won't kill
anyone.

Furthermore, having switched to a filesystem VFS I'm again out of memory...
[Tue Nov 29 15:12:48 2011] [error] [client 72.225.228.193] PHP Fatal
error:  Allowed memory size of 402653184 bytes exhausted (tried to
allocate 84 bytes) in /usr/share/horde4/kronolith/lib/Kronolith.php on
line 698, referer: https://mymail.example.com/login.php

So it' seems I need to increase to 512.  Or go back to a SQL VFS?  Or
perhaps try the other option?

Simon