JCoglan's faye (bayeux for node.js) has some built-in "intervals", i.e. timers, which regulate connection reuse and how messages end up bundled together in bulk

JCoglan's faye (bayeux for node.js) has some built-in "intervals", i.e. timers, which regulate connection reuse and how messages end up bundled together in bulk transmissions -- this can cause an apparent increase in latency, I've run into this problem myself. By changing the interval and reconnection settings one can reduce the latency, but there are some side-effects, i.e. the faye-client connection seems to become less stable. I've poked around in the faye codebase myself -- it's non-trivial to try and pull it apart. I've not yet had success in figuring out what could be changed to enhance the library in its service as a near-real-time messaging transport for high bandwidth, very high message count use cases. The author seems to be a very busy man, but if enough intrest was shown, JCoglan might be willing to work on optimizing it (and documenting it) further. In a local network setting, in various tests, I've had at times 40Mbps, with message rates in excess of 10,000 requests per second flowing through a single faye process. The latencies were on the order of 10-100 ms And this was sustained over a period of hours.