[erlang-questions] Garbage Collection, BEAM memory and Erlang memory
Fri Feb 20 15:11:20 CET 2015
Given the amount of answers I got in this post, I want to follow up and
give some additional information.
After struggling for quite a while, I just did a comparison between using
SSL connections vs standard TCP connections.
The results are quite impressive.
This is the diagram of memory evolution for a system under load, with SSL:
This is the same system, but without SSL:
You can clearly see that using standard TCP connections the system is
Using SSL connections, on the other hand, results in RAM memory having very
erratic behavior that ends up blowing up the node.
Not sure what to do with this information, except that I'm going to use a
SSL termination (HAProxy or ELB) and have my Erlang node run without SSL.
If anyone is curious just ping me.
On Wed, Jan 28, 2015 at 8:09 PM, Roberto Ostinelli <
> That's a valid point, and I can clarify.
> During the first phase, all the long lived connections are made. During
> the second phase, newly-created short lived connections send messages to
> the long lived ones.
> The long lived connection are all connected when the first memory increase
> phase ends, which is when the short-lived connections start sending
> What is unclear to me is why the second memory increase phase happens
> quite some time after these short lived processes have started sending
> > On 28/gen/2015, at 20:02, Anton Lebedevich <mabrek@REDACTED> wrote:
> > The graph looks really weird for me assuming that the load applied to
> > the system is stable. Why does it go down for a short time and then
> > jumps higher than it was?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions