[erlang-questions] Get to know your Erlang memory allocation

Bob Ippolito <>
Thu Nov 7 22:16:25 CET 2013


Did you try using binary:copy/1 at all? Last time I had this issue, that
function wasn't around, but it seems like it might be useful for your use
case.

Some of the other strategies we've used to work around these kinds of
issues are:

* Use a temporary process for operations that will generate a lot of garbage
* When that doesn't or can't work, include a manual hibernate or
erlang:garbage_collect/0


On Thu, Nov 7, 2013 at 10:17 AM, Fred Hebert <> wrote:

> In the same vein as Rich Carlsson's recent post on understanding how
> erlang:get_stacktrace() works, I decided that this list would probably
> be interested in reading this blog post about some of the work we do
> with Erlang at Heroku:
> https://blog.heroku.com/archives/2013/11/7/logplex-down-the-rabbit-hole
>
> The reason I post this here is that if you scroll down enough, you'll
> meet an entire section devoted to understanding (from afar) how Erlang's
> memory allocators work, and how they could be tuned.
>
> It's something I have to thank Lukas Larsson for, given he's the one who
> helped us understand all of this and solve important memory issues we
> had.
>
> I hope you enjoy the read!
> Regards,
> Fred.
> _______________________________________________
> erlang-questions mailing list
> 
> http://erlang.org/mailman/listinfo/erlang-questions
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20131107/8b7e4e0d/attachment.html>


More information about the erlang-questions mailing list