You have to be careful with Node because being single threaded but highly async, you could be running anywhere from ten requests per process down to three processes per core and one request per process, depending on workload.
But I’m in a similar boat, and when I think about our ratio of cores to requests per second, it’s scandalous.
When a problem is big and the patterns are set, there’s not much you can do, and the people I flag as potential recruits have a habit of quitting instead of diving onto this grenade. I have learned all new ways that some known (to me) anti patterns can screw you over.
And it grates that Tony Hoare said this 40 years ago:
I conclude that there are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies and the other way is to make it so complicated that there are no obvious deficiencies.
If something stays slow it’s because someone worked their butt off making sure that none of the deficiencies were obvious.
But I’m in a similar boat, and when I think about our ratio of cores to requests per second, it’s scandalous.
When a problem is big and the patterns are set, there’s not much you can do, and the people I flag as potential recruits have a habit of quitting instead of diving onto this grenade. I have learned all new ways that some known (to me) anti patterns can screw you over.
And it grates that Tony Hoare said this 40 years ago:
If something stays slow it’s because someone worked their butt off making sure that none of the deficiencies were obvious.