3 ms·
This could have been solved with a simple addition of another queue. Don't spawn off heavy requests without a throttle / queue, or else you will overload your
by chadscira 10y ago
This could have been solved with a simple addition of another queue.
Don't spawn off heavy requests without a throttle / queue, or else you will overload your single core.
We normally don't think about this because most requests are just tiny queries / small http requests.
- ericj5 10y agoThis. It sounds like the author used a queue and worker pool with the Go version. There's nothing stopping you from doing the same thing in Node. I think a lot of people forget this sometimes and just spawn off unlimited multiple simultaneous requests in Node apps. Doesnt matter what language you're using, that's never going to turn out well