Closing TCP/SSL connexion or let the VM close it
Fri Dec 18 12:35:39 CET 2020
On Fri, Dec 18, 2020 at 10:26:57AM +0100, Frank Muller wrote:
> Thanks Guilherme.
> Anyone else?
> N.B: I’m having troubles to reach this mailinglist. It’s said mailmain
> can’t find module gd
Oh, did that leak out!?
While we had that fault I had to dig through the webserver logs with
Mailman claiming that for security reasons it would not show me the
Should be fixed now. We upgraded the server and cleaned out some stuff
that was used any more, except that Mailman still imported gd but did not
Thank you for letting us know.
> Thur . 17 Dec. 2020 19:38, Guilherme Andrade <g@REDACTED> wrote :
> > Hello Frank,
> > AFAIK, the only difference is that, when letting the VM take care of it,
> > monitors will be triggered and delivered to the connection owners (whether
> > SSL processes or TCP ports.)
> > What kind of impact that will have on performance is unknown to me - I
> > suppose only measurements could tell.
> > (Unless you're explicitly `gen_tcp:shutdown`ing or `ssl:shutdown`ing your
> > connections in order to try and flush the send buffers - in that case, I
> > expect there will be a difference.)
> > On Tue, 15 Dec 2020 at 07:14, Frank Muller <frank.muller.erl@REDACTED>
> > wrote:
> >> Hi guys,
> >> I’m wondering if my processes should explicitly close the TCP/SSL
> >> connexion they hold before exiting or should they let the VM handles that?
> >> Does it make any difference?
> >> I’ve a bunch a processes in my app (around ~15K per at any even time).
> >> /Frank
> > --
> > Guilherme
/ Raimo Niskanen, Erlang/OTP, Ericsson AB
More information about the erlang-questions