You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I have some issues with this library and the number of connections it creates. I don't know exactly if the library is the problem or my configs but I was doing a simple test with
If only 4 sockets timed out why did it create 18 ? Shouldn't have been 9 there ? The initial 5 sockets and the additional 4 that were replaced because they timed out. Btw, the numbers vary on every run. What am I missing here ?
Yes, unless there is activity on it so it doesn't time out. So only 4 sockets timed out, and if they needed to be recreated, a maxim of 9 sockets should have been created in total, or anywhere between 5 and 9 if some of those 4 timed out sockets expired and the end of the test and had nothing left in queue. So why 18 ?
also i get an error like this
(node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit.
the stack trace indicates _http_agent.js:214:10 and agent.js:107:20
and for HTTPS connections, it uses the certificate files as keys in the getName function. The application i use this in, has one 50KB certificate file with all the certificates. The log increased to 1.5 GB in less than a minute. Why in the world you would use the content of the certificates and keys as the key to the map ?
I too would like to run this library through some perf tests. I know this thread is a little stale, but @fengmk2 can you post the scripts, versions, etc you used for testing?
Activity
fengmk2 commentedon Jan 29, 2015
keepAliveMsecs:100 meaning a free socket not active for 100ms it will close.
cthackers commentedon Jan 30, 2015
Yes, unless there is activity on it so it doesn't time out. So only 4 sockets timed out, and if they needed to be recreated, a maxim of 9 sockets should have been created in total, or anywhere between 5 and 9 if some of those 4 timed out sockets expired and the end of the test and had nothing left in queue. So why 18 ?
fengmk2 commentedon Jan 30, 2015
can you show me the
closeSocketCountandrequestCountvalues?cthackers commentedon Feb 2, 2015
I don't have such values in the result. I use version 0.2.3.
cthackers commentedon Feb 3, 2015
also i get an error like this
(node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit.
the stack trace indicates _http_agent.js:214:10 and agent.js:107:20
cthackers commentedon Feb 3, 2015
and for HTTPS connections, it uses the certificate files as keys in the getName function. The application i use this in, has one 50KB certificate file with all the certificates. The log increased to 1.5 GB in less than a minute. Why in the world you would use the content of the certificates and keys as the key to the map ?
fengmk2 commentedon Feb 6, 2015
can you show me your demo codes, node version and agentkeepalive version, I want to repeat what your meaning.
DesignByOnyx commentedon May 1, 2015
I too would like to run this library through some perf tests. I know this thread is a little stale, but @fengmk2 can you post the scripts, versions, etc you used for testing?