High Erlang memory binary

[Alin Popa]

Thanks Mike,
In fact that's a good point, even though I was aware of this, haven't spent
much time looking at those things, so will add it to my list.

Alin

On Tue, Jan 14, 2020 at 11:59 AM Mike Benza <mikebenza@REDACTED> wrote:

> Alin,
>
>>
>> 3. Any other suggestion on what I might be doing wrong?
>>
>
> I ran into a similar problem a few years ago.  I was using jiffy to decode
> JSON blobs.  Jiffy gave me back sliced binaries from the original binary I
> passed in.  This kept the whole binary in memory, even if I was just using
> a tiny portion of it and discarding the rest.  If you're doing this
> (unlikely that you've run into the exact same problem), use the
> copy_strings option to jiffy.
>
> If not, consider looking for other cases where you start with a large
> binary, discard most of it, and keep a small portion of it.  That may be
> the cause of your binary bloat.  If you find something like that, try
> copying the binaries in a way that causes the original binary to be
> released from memory.
>
> - Mike
>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20200114/fb62f8a5/attachment.htm>