DEV Community

Discussion on: Performance aspect of Deno vs. Node

Collapse
 
eunovo profile image
Oghenovo Usiwoma

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.

Collapse
 
liamjoneslucout profile image
liam-jones-lucout

Spot on.

Collapse
 
gjuoun profile image
Jun Guo • Edited

Very good point!

Well, you are right. After rethink and a few tests, I should update my post a little bit.

Collapse
 
beaumontjonathan profile image
Jonathan Beaumont

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.

Thread Thread
 
gjuoun profile image
Jun Guo • Edited

Thanks for the comment. Sorry about that.
I should have done more research and make it more clear.

Thread Thread
 
beaumontjonathan profile image
Jonathan Beaumont

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 🎉

Collapse
 
iainjreid profile image
Iain J. Reid

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!