You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I was looking at the code that was being executed after reading in the express.js benchmark page that the app did not scale well with additional cores. I don't think cores is always relevant to every single app out there. Node.js actually has a feature that allows you to cluster additional instances of a service together. But these are child processes. So cores doesn't matter when we are talking about a process. They don't translate to convey something meaningful.
The code for this app could also mimic the best case happy path that a company could hope to achieve. For example, we could use a setTimeout for 100ms to replicate going to a database and retrieving something and then return a json object. I would be happy to contribute this work as well!
The text was updated successfully, but these errors were encountered:
Hello, I was looking at the code that was being executed after reading in the express.js benchmark page that the app did not scale well with additional cores. I don't think cores is always relevant to every single app out there. Node.js actually has a feature that allows you to cluster additional instances of a service together. But these are child processes. So cores doesn't matter when we are talking about a process. They don't translate to convey something meaningful.
The code for this app could also mimic the best case happy path that a company could hope to achieve. For example, we could use a setTimeout for 100ms to replicate going to a database and retrieving something and then return a json object. I would be happy to contribute this work as well!
The text was updated successfully, but these errors were encountered: