2 ms·
The memory seems high actually, I've seen other C / C++ / Go implementation using less than a 1GB for 1m connections. Pretty cool nonetheless! https://github.c
by Thaxll 8y ago
The memory seems high actually, I've seen other C / C++ / Go implementation using less than a 1GB for 1m connections. Pretty cool nonetheless!
https://github.com/uNetworking/uWebSockets https://github.com/uNetworking/uWebSockets
https://speakerdeck.com/eranyanay/going-infinite-handling-1m-websockets-connections-in-go?slide=35 https://speakerdeck.com/eranyanay/going-infinite-handling-1m...
- lganzzzo 8y agoThanks, In this benchmark I decided to go without much of the framework tuning. Mostly took it as is in order to see what I can get. In any case oatpp is general purpose web framework, it is understood that dedicated libraries like uWebSockets may be more optimized. Nevertheless I beleve it's still much space for tunning and optimizing of oatpp.