uWebSockets

i was initially confused how 19.2K rps is notable when Express typically benchmarks around 15K rps [1]. however, the author is benchmarking a route with an id param here, not a static route. [1] https://github.com/uNetworking/uWebSockets/discussions/1415

And consider a socket.io alternative that emphasizes performance: https://github.com/uNetworking/uWebSockets

pure raw metal It means exactly what it means. If I get a pure bare metal server, will that computer simply handle more requests than a Go or a Node server (assuming the same single-threaded paradigm)? That's the only reason I'd ever consider moving away from the ergonomics of something like Node or Python, if my bare metal server can save me money by simply handling more requests with less cpu/memory. Edit: Thanks for that link though, just got turned onto this: https://github.com/uNetworking/uWebSockets/blob/master/misc/...

They use uWebSockets (https://github.com/uNetworking/uWebSockets), which was written in C, but has an interface to use in NodeJS. It's been really performant for me in my simple tests compared to other popular websocket libs that slow down fairly quickly.

The already insanely fast (probably the fastest) http/websocket server uWebSockets is seeing a 40% improvement with io_uring in initial tests! https://github.com/uNetworking/uWebSockets/issues/1603#issue...

Not exaclty -- it looks like it's pretty overkill for my needs I'm looking for something more like websocketpp[0], or even just grpc without a requisite proxy. uWebsockets looks really promising, being header only, but in the fine print requires a runtime library. unfortunately, none of that ecosystem seems to use cmake, making integrating it that much more of a pain. why use cpp for this, I'm sure some HNer will ask. the ray tracer itself is using cuda, that's why. I've also debated - running it as a grpc server and having some proxy in a more web-accessible language - creating python bindings and using python to make a websocket/http server for it neither of those are out of the question, but they're not my first choices, because I'd like to keep the build & execution simple. introducing dependencies, especially other executables,

Really cool i also made and CAPI for using WebSocket in C, https://github.com/uNetworking/uWebSockets/tree/master/capi I will take a deep look on your project thanks for sharing!

The first link on the page explains exactly what it is, and what the motivations are. https://github.com/uNetworking/uWebSockets/blob/master/misc/...

For those who didn’t know, uWebSockets is one of the reasons for Bun’s high performance in server benchmarks [1], not just JavaScriptCore. [1] https://github.com/uNetworking/uWebSockets/discussions/1466#...

Cool little library, I'm using it, but author has an ego the size of Wolfram's. This is just one snippet, there are many if you rummage through the docs and issues: > In the 1970s, programming was an elite's task. Today programming is done by uneducated "farmers" and as a result, the care for smart algorithms, memory usage, CPU-time usage and the like has dwindled in comparison. https://github.com/uNetworking/uWebSockets/blob/master/misc/...

Seeing the example[1], I suddenly realised how nodejs and C++, which started so far apart, are slowly merging into one language... [1]: https://github.com/uNetworking/uWebSockets#battery-batteries...

Lots of reasons: - Code cleanliness: their code almost looks like code golfing. Hard to debug. - Dependencies: everyone has different ways of implementing everything. some are even outdated. some even have stale bots that close legitimate but unattended issues. - Performance: fastify and uWebSockets.js beats express.js on benchmarks. see https://www.fastify.io/benchmarks/ and https://github.com/uNetworking/uWebSockets/tree/master/bench... - Multi-part parsing: this is built-in with uWebSockets.js. on express your options are multer or busboy. - WebSocket Server support: this is built-in with uWebSockets.js. on express your options are using ws and socket.io. - WebSocket pub/sub: built-in with uWebSockets.js There are better alternatives like the following: - https://www.fastify.io/ - https://github.com/uNetworking/uWebSockets.js - https:/

Some of Bun's server speed can be attributed to uWebSockets, which has node bindings [1]. Of course this is just a small detail, since Bun is a huge project. [1] https://github.com/uNetworking/uWebSockets/discussions/1466#...

Ok Alex Huntman (creator of uws) and Jarred Sumner (creator of bun) exchange some words here [1]. It turns out Bun is using uws under the hood. [1] https://github.com/uNetworking/uWebSockets/discussions/1466