3 ms·
16k r/s is not trivial to get for a non-hello-world app on NodeJS even on a big server, but if you read the article you'd see it's actually about a quarter of t
by KirinDave 9y ago
16k r/s is not trivial to get for a non-hello-world app on NodeJS even on a big server, but if you read the article you'd see it's actually about a quarter of that.
... Yeah basically it is an article about using concurrency.
- qaq 9y agoI was not obviously commenting on the content but on a trend of coming up with measurements that make for a catchy title.
- KirinDave 9y ago> 16K/sec is typical for a node app on fairly avg server. This certainly doesn't read like "I'm talking about the title" to me. Also, in other parts of the thread you take performance questions seriously, further diluting the impression your post was about the title or phrasing.
- qaq 9y agoThe title is presenting handling 16K/sec as something special my only original point was that the author is using per minute metrics to make numbers look more impressive. It's very possible that I did a very poor job of making that point :). My comment that I am sure Go more performant than node was beign downvoted so that took things in a diff. direction.