Talking about performance is cool
A few days ago, I read Craig Morten's post: What Is The Best Deno Web Framework? It gives an overview ...
For further actions, you may consider blocking this person and/or reporting abuse
Hi! You mentioned that Deno should be slower because it has to type check at compile time. I understand compile time to be different from runtime. Unless type-checking is done at runtime, I don't see how it should affect the runtime performance of Deno.
It's also worth point out that runtime types can have a large positive effect on performance.
The more information the runtime has about the code that it's executing, the more optimisations it can apply whilst the application is cold!
Spot on.
Very good point!
Well, you are right. After rethink and a few tests, I should update my post a little bit.
Hey man, you should really update this post instead of writing another (or at least add a disclaimer and link to the comment thread). It is super confusing to share misinformation publicly.
Deno has different performance to node because it a different implementation; the server internals are written in rust as opposed to C/C++, and hasn't been optimised heavily yet. A quick GitHub issue search actually shows that several recent PRs have improved performance lately, but I digress.
With respect, you really shouldn't be writing a blog post about performance if you don't know the difference between compile time and runtime.
Thanks for the comment. Sorry about that.
I should have done more research and make it more clear.
Nice one man! Reading this back, sorry if that comment came across a little harsh. I've read a lot about deno but haven't had the time to build much yet, so kudos. Keep on posting 🎉
My understanding of the benefit of "node" is a high I/O performance during the heavy traffic scenario compared to the other language/frameworks with relatively fewer codes, and I think "Deno" is aiming better "Node". Based on that purpose/goal of "Deno", That's a good thing that Deno has higher performance in the heavier traffic than Node.
Hinestly, I have been looking for a post on Demo vs Node performance for a while now, thank you for writing this.
V8 is V8, what you should be doing is comparing build/parsing time.
Does HTTP2 make things easier?
Not in this scenario, no. Autocannon is used to test concurrent unique users, rather than just one user hammering the API.
The main improvement with HTTP2 is reducing the number of roundtrip requests that a single user might make (by reusing the TCP connection), but it doesn't have any meaningful effect on a group of unique users. Hope that helps!
It would be an interesting test though, to see if there was a meaningful difference. But I'm doubtful, because the biggest overhead in an HTTP request is the TCP connection itself.
Deno claims to be a better nodejs, but it can only be a different nodejs if it can't beat nodejs' performance! At least before the author makes the improvement (which potentially could never happen)!
If it's the same performance-wise but can still offer other benefits, it would still be considered better. Also hello world tests are virtually meaningless, I feel 🤔
This middleware for Deno brings good results: deno.land/x/faster