-
Notifications
You must be signed in to change notification settings - Fork 646
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add uWebSockets.js (Node) #1064
Comments
I think this could be categorized as node, since app are written in javascript |
can we do an HTTP1/1 app with uWebSocket => without SSL ? |
I don't know, I can't find about that in the source code and docs |
I'm not against adding this here, but flagged as experimental since not "native" |
its stable now . i tested nodejs version , it have awesome performance ! it handled more requests than Go-FastHttp and Rust-Actix with less memory usage . |
@mahdisml what I meant bu saying thus, I'm happy to read any /cc @aichholzer |
@alexhultman Did you consent of adding |
You are making mistakes in your benchmarking, node (12.7) | sifrr (0.0) | 176261.33 | 155.18 MB 176261 is not "better" than 175676. They are the same. They are insignificantly different. You are not reporting CPU-time usage, so it is impossible to debug why they are the same, but I bet you are making the same exact mistake TechEmpower make; You're not keeping track of CPU-time usage so you cannot keep track of when other parts bottleneck (such as your networking set-up). You end up making the same mistake as TechEmpower do; you benchmark nothing but noise. The difference between 176261 and 175676 is nothing but random noise. Like reporting the background radiation from universe as significant data points in an experiment. Also that number is unreasonable for 4 CPU cores. I bet you are seeing like 40% CPU-time usage, basically idling. I did compile and run agoo-c and siffr here locally and agoo-c is without a doubt significantly faster than siffr: Running 10s test @ http://localhost:3000 Running 10s test @ http://localhost:3000 These are 1 single CPU-core at 100% CPU-time on a shitty laptop 8 years old. For reference point, I also benchmarked 碌WS (the C++ project) and I got this: Running 10s test @ http://localhost:3000 TLDR; 碌WS.js and siffr are significantly slower than agoo-c and I do not feel like having 碌WS.js listed in the top based on nothing but random noise and other bottlenecks. Same reasons I don't participate in TechEmpower; quantity over quality and in-depth analysis. Thanks |
What I'm saying is, https://www.techempower.com/benchmarks/#section=data-r18&hw=ph&test=plaintext This test as linked above is completely botched and nonsensical as the top 17 servers all score identically at 99.9%. That is, they are being capped, truncated. It's like measuring for the tallest man on earth but only bringing a 2 meter long tape measure and then reporting people's length with nanometer precision from that. 2 meter and 0.000000000000004 nanometer It gives you entirely and utterly botched results. |
i think Ram Usage is also important and forgotten in this benchmark and TechEmpower ! |
@alexhultman @mahdisml sure we will add @alexhultman as I understand, you did not consent having |
@alexhultman on |
That's incorrect, the chart states CPU-time normalized. Anyways, No I do not want uWS.js to be listed here as I explained very thoroughly it would be entirely pointless and inaccurate. Thanks |
But what about RAM consumed ? But, anyway, I'll respect your decision and I'll ping you when this project is more stable 鉂わ笍 |
There is no point in continuing this. I think you're doing pseudo-science here, failing to understand what you are actually trying to measure and why. Thanks |
no we are going steps by steps @alexhultman we are completely aware that the results are not ready to be usable, but which project could claim to be stable at his youth 馃槢 resource usage will be added (but I do not know when because I'm the only No need to argue here, but no need to defame any project. The maturity of 鉂わ笍 |
I can see that your results now show a significant difference between agoo and sifr. Did you change something? |
@waghanza Sorry to ping you but, When I checked last time you had these results:
and now you have these
showing a completely different outcome. Did you fix anything here? Now the results at least fall in the correct order. |
@alexhultman with the new changes do you consent the use of uWebSockets.js here? |
@alexhultman The above table is sorted. The order is dynamic and could change by two things :
BTW, the table has change, we now only display |
Now you're listing sifrr at 164423 and agoo-c at 143936. These are highly chaotic reports, entirely contradictory to past reports. You could get more reliable data points by sampling the aurora. I have no interest to partake in nonsensical pseudo science. |
no arguing @alexhultman, I was just explaining why the order switch ... and moreover, we are not yet in production, using |
It claim faster than fasthttp (go) and maybe can beat japronto for requests per seconds 馃槈
The text was updated successfully, but these errors were encountered: