4 ms·
Surprised to see such mediocre performance from Node. It was an engineering decision on our team to develop one of our Lambdas with Node and we were deciding be
by muh_gradle 5y ago
Surprised to see such mediocre performance from Node. It was an engineering decision on our team to develop one of our Lambdas with Node and we were deciding between Python and Node. Looks like Go and Rust look very promising.
- Jamie9912 5y agoAgreed, especially when you can run Javascript without cold starts at all on Cloudflare Workers
- ignoramous 5y agoOP should have tested Deno (https://github.com/denoland/deno https://github.com/denoland/deno) too along side Node. Alas...
- Zababa 5y agoDeno uses v8 too, that would be just comparing libuv to Tokio.
- rough-sea 5y ago> just As if everything else is the same. It is a completely independent code base.
- Zababa 5y agoWell, the performance seems to be mostly the same https://mayankchoubey.github.io/Deno-vs-Node-Performance/ https://mayankchoubey.github.io/Deno-vs-Node-Performance/. > It is a completely independent code base. Not exactly, the heavy lifting is done by v8 on both sides. Deno can do lots of things around the ergonomics, and switch around the event loop (though libuv is already pretty good), but outside of that they are mostly equivalent.
- deleted 5y ago[deleted]
- ignoramous 5y agoThat blog post is damning! Thanks for sharing it. btw, deno publishes its own benchmarks: https://deno.land/benchmarks https://deno.land/benchmarks
- traspler 5y agoI was also quite surprised, other benchmarks I‘ve seen before have shown it to be just slightly behind Python.
- nodejs_rulez_1 5y agoI am not surprised that a re-purposed browser engine sucks for back-end.
- muh_gradle 5y agoThe event driven architecture for NodeJS with simple requests like the test performed fits Node usage. I've seen past cold-start tests like this (admittingly it's been a while), and Node and Python are often the leaders of the pack with Java being the worst.
- deleted 5y ago[deleted]