100% CPU and server crashes after connecting 10k clients about aedes HOT 10 CLOSED

Yes, this is perfectly "normal", and described in #60.
Most of the code is highly synchronous for performance reason, but it might use a process.nextTick in a couple of places (like in the memory persistence).

PR is welcomed.

from aedes.

@mcollina It's normal that Aedes is unable to handle 10k connections? Am I doing something wrong?

Or is the MemoryPersistence unable to handle 10k connections?

from aedes.

It's normal that it crashes with RangeError: Maximum call stack size exceeded.
It's not looping, Aedes works heavily on the stack, specially with the in-memory mq and persistence.

node --stack-size=X solves this, where X is big enough.

wrapping the callbacks in process.nextTick in the memory persistence will probably solve your issue.

from aedes.

I ended up going with mqtt-connection since I don't need any kind of persistence. Seems to work well so far for me.

from aedes.

Perfect, I'm closing this now.

from aedes.

Hey, I'm facing a similar issue after 15k connections.The process becomes unresponsive for quite some time and then starts working again. I'm not sure if gc is the culprit here as it is synchronous and takes quite a bit of time.

from aedes.

@GavinDmello with the same error? what is the memory usage? Can you produce a script to reproduce artificially?

from aedes.

The server doesn't crash in my case and memory is well under control. It's just the CPU which is cranking up to 100 % and stays there with nothing happening(no logs) and comes back to normal after some time.

from aedes.

@GavinDmello if I can reproduce, I can help fixing it. Tools like http://npm.im/0x, dtrace, perf, etc, are built to solve those kind of issues.

from aedes.

related to #88

from aedes.