-
|
I'm assuming uWebSockets is faster than uWebSockets, since it's written in C++. Just a little question of curiosity came into my mind wondering how much times better would uWebSockets be than uWebSockets.js Since I don't really know much C++, I'm wondering if anyone here could do the actual experiment of it (determining how much times it would be faster). |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
They both use the same library underneath, that is the whole point. If you call
Receiving large number of websocket message events is more efficient staying in C++ than switching between C++ and JS |
Beta Was this translation helpful? Give feedback.
They both use the same library underneath, that is the whole point. If you call
app.publish()it will broadcast messages the same way with the same speed. Most of any difference is all the stuff you stack on top to code your app, your JS will be less efficient depending on what you add. If you minimize your JS it can also be fast. The ease of coding with JS especially with async promises and things like worker threads with Node make it a better option for meReceiving large number of websocket message events is more efficient staying in C++ than switching between C++ and JS