News for hackers. Stuff that matters.
Re:uWebSockets: Scalable WebSocket server library for Node.j... by alexhultman on Friday May 20, 2016 @09:49AM (#11737728)
Also - this server passes the entire Autobahn with no fails, passes Engine.IO tests, Primus tests and exits gracefully with no Valgrind issues. Also, it builds with no warnings. Also, it has been running for weeks stable.
Re:uWebSockets: Scalable WebSocket server library for Node.j... by IIlllIllIIIIlII on Friday May 20, 2016 @09:57AM (#11737793)
Can I ask why you choose to implement your own queue when many exist within C++? (e.g. using queue<T> or list<T>)
Re:uWebSockets: Scalable WebSocket server library for Node.j... by alexhultman on Friday May 20, 2016 @10:06AM (#11737852)
Memory footprint and performance.

This implementation is way, way more lightweight. And it assumes that the buffer being queued has a struct Message in its head, so it doesn't have to allocate a node - one memory allocation is therefore skipped.