High memory usage in vibe.d application

[rikki cattermole]

On 30/06/2018 7:42 PM, Anton Fediushin wrote:
> On Saturday, 30 June 2018 at 05:00:35 UTC, rikki cattermole wrote:
>> On 30/06/2018 4:49 AM, Bauss wrote:
>>> I wouldn't really blame the GC. There is a higher chance you're just 
>>> not using it how it's meant to be, especially since it looks like 
>>> you're mixing manual memory management with GC memory.
>>
>> Let's be honest, I don't think it was meant to live in a container 
>> with 64mb of ram. I just don't think it is kicking in to collect.
> 
> It doesn't, I'm experimenting with different GC configurations [1]. By 
> default [2] `maxPoolSize` is set to 64MB, so maybe program gets killed 
> by docker right before GC decides to collect.
> 
> [1] https://dlang.org/spec/garbage.html#gc_config
> [2] https://github.com/dlang/druntime/blob/master/src/gc/config.d#L23

The OS ext. takes memory too.

34mb might be safer.