connection_closed_abruptly

[mkozjak]

Even with the latest amqp library, I still get this.

[PuKoren]

+1, lots of connection close errors

[mkozjak]

I do not recommend this library for production uses. Had lots of problems with it. Memory leakage is huge (because of its dependency, 'amqp').

After some time profiling the memory, I ended up rewriting the whole project without rabbitmq.

[PuKoren]

We made our own RPC implementation in the meantime:
https://github.com/dial-once/node-rabbitrpc

[mkozjak]

Lookin' good! :)
Have you used this in production? amqplib should perform nice. :)

[PuKoren]

It is in production ATM yes, but not tested on modules with more than 100 msg/sec yet

[mkozjak]

amqp made problems even with a few msgs per second. I had 10mb per minute memory growth.
Do you see any abnormal memory consumption with your wrapper so far?

[PuKoren]

I wrote a benchmark on the module since you asked for it, if you are interested you can launch it with node test/benchmark.js

Memory climbs from 37MB to 91MB and then stops to grow. The process took almost 800 sec and you can see the lasts ticks on my machine:

Running for: 780.071 secs. Current tick: 77
Current bitrate (this tick): 93.5 /sec.
Memory usage: 91983.872 kb
Running for: 790.072 secs. Current tick: 78
Current bitrate (this tick): 95.1 /sec.
Memory usage: 91983.872 kb
Running for: 800.073 secs. Current tick: 79
Current bitrate (this tick): 97 /sec.
Memory usage: 91983.872 kb
Running for: 810.074 secs. Current tick: 80
Current bitrate (this tick): 95.4 /sec.
Memory usage: 91983.872 kb
Running for: 820.075 secs. Current tick: 81
Current bitrate (this tick): 94.9 /sec.
Memory usage: 91983.872 kb