4 ms·
I really liked using dnode, but I had serious scalability problems with it. I didn't have time to look too closely, but I found quite significant latency betwe
by CoffeeDregs 15y ago
I really liked using dnode, but I had serious scalability problems with it. I didn't have time to look too closely, but I found quite significant latency between sending/receiving messages to the extent that I just downgraded to using socket.io directly and was quite happy. Sorry to be vague, but it's been 8 months since I experienced the issue.
Definitely, give dnode a go. It's a lovely piece of software, but keep an eye out for performance issues.
- NinetyNine 15y agoSame here, we had to abandon usage of it in favor of a simple json-tcp bridge. We were looking at 100ms+ for communication between two ec2 instances; with straight tcp it was closer to 7ms.
- NinetyNine 15y agoSame here, we had to abandon usage of it in favor of a simple json-tcp bridge. We were looking at 100ms+ for communication between two ec2 instances; with straight tcp it was closer to 7ms.