electrode-io/electrode-keepalive

node.js HTTP agent with customized keep alive

electrode-keepalive's Issues

Should Expiry be more or less than keepAliveMsecs?

Just curious if there are any known quirks. I know we're dealing with two things here, expiry of DNS cache and pinging the server to keep it's sockets open every n msec but have there been any noticeable behaviors where one should keep expiry or keepalivemsec at a particular threshold over the other for

Memory Leak

Team,

I wanted to inform you that since we introduced electrode into our code we noticed pretty drastic memory leaks which caused us to revert our changes. While preliminary review of the code doesn't show anything obvious, the evidence is clear.

This graph shows our memory metrics of our UI application, which a partnered API also saw the same memory decline. No other code changes were introduced. You'll notice the flat line is a set of servers that don't have the module while the rapid decline includes electrode.

Same is true for our regularly deployed development environment (flat lines are other non-prod environments)

We followed your implementation instructions completely. Since removing electrode, our memory is flat.