Possible memory leak about aedes HOT 11 CLOSED

I will have a look. BTW, a latency tester is a nice OSS project that might benefit the community.
Also, check out https://github.com/mcollina/native-hdr-histogram.

from aedes.

The value should be dimensioned on how slow your clients are.
This is a bug, in the sense that it should not be shown as a warning, but rather through some events and the like. I'll put some thinking into it.

from aedes.

What are you using to send those messages? I couldn't replicate that behavior myself.

Have you seen an increase in memory?

Your fix will likely create a memory leak, because those callbacks needs to be callled.

from aedes.

What are you using to send those messages? I couldn't replicate that behavior myself.

Have you seen an increase in memory?

Your fix will likely create a memory leak, because those callbacks needs to be callled.

from aedes.

I'm using the standard mqtt client(Mqtt.js) and No significant changes in memory

from aedes.

Can you please upload your script, so I can reproduce?

from aedes.

Here is the link of the sample clients I'm trying to connect with :

https://gist.github.com/GavinDmello/d614940e0f89383f3f471b90ec121360

from aedes.

@GavinDmello can you please upload the code of your broker? because of this line https://github.com/mcollina/aedes/blob/master/aedes.js#L43 the warning should not appear.
(try increasing that factor, that is the correct way to do it)

from aedes.

I increased the concurrency factor to 1000 which solved the issue. What should the ideal factor be if I'm expecting a max concurrency of 50k messages/sec .

from aedes.

Closing, as I think this was solved. Feel free to reopen.

from aedes.

@mcollina Possibly this is the same issue as #88

from aedes.