6 ms·
That's not the message of the article. The original application wasn't poorly written. In fact it was written by people who know Javascript and refactored multi
by mrweasel 10y ago
That's not the message of the article. The original application wasn't poorly written. In fact it was written by people who know Javascript and refactored multiple times. The new application is written by someone that picked up Go in a few weeks.
I don't see it as a criticism Node.js either, it's just that Node wasn't the right tool for the job, in this case. If you pick the correct tools and know the limitations of your tools, then it becomes less important how proficient you are with those tools (not irrelevant of cause).
- chadscira 10y agoI would like to know more about the implementation. I have had node do 12000 requests a minute with no problem (on a single core). In this case they had 4 two core boxes, so they needed each one to at least perform 42 requests a second under max load. I want to know more :)
- justsumbody 10y agoThat's not really that fast... and probably doesn't hold up anyway under diverse request types. http://marcio.io/2015/07/handling-1-million-requests-per-minute-with-golang/ http://marcio.io/2015/07/handling-1-million-requests-per-min... etc
- supermatt 10y agoIts evident from the flamegraph that the architecture is fundamentally different. Why are the stacks so deep in the javascript example? Why aren't they using a similar worker pool in the node implementation? Are they just throwing everything onto the event queue and treating that as a naive worker pool? If you know the limitations of your tools then you can work around them. This was clearly not done in this case.