3 ms·
> The difference in the code I’m working with is being able to handle 250 req/s in node versus 50,000 req/s in Go without me doing any performance optimizations
by vorpalhex 5y ago
> The difference in the code I’m working with is being able to handle 250 req/s in node versus 50,000 req/s in Go without me doing any performance optimizations.
Your node code should be in the 2k reqs/s range trivially, with many frameworks comfortable offering 5k+.
It is never going to be as fast as go, but it will handle most cases.
- throwaway894345 5y agoHow can you make these claims without information about what his application handles requests? Not everything is a trivial database read/write op.
- hsn915 5y agoesbuild is 100x faster than js build tools, so in general 100x speed up sounds about right.
- randomdata 5y agoSucrase, written in Typescript, claims to be 2x faster than esbuild. I'll leave you to your own benchmarks.
- morelisp 5y agoSucrase does this by removing some things you might expect to be table stakes, like detecting invalid parse trees and complete JS syntax. Pragmatically, esbuild can also start faster and parallelize, which means shorter wall-clock builds.
- randomdata 5y agoSure, but esbuild also drops features found in the compared tools to gain a performance edge. The language may bring some marginal difference, but it's clear that the algorithm is the most significant piece.