Great article.
How do you think when we deploy nodejs app on openshift?
As we know, we can configure the CPU size and scale up the services.
Is this will increase apps performance with UV_THREADPOOL_SIZE config ?
So, with my limited knowledge of OpenShift, when you re-configure your CPU size, your node app doesn't get restarted and remains in memory. Therefore, it will not take advantage of the new CPU cores until it's rebooted.
However, if you autoscale your node services in that OpenShift spawns new replicas, then the new replicas will take advantages of the new CPUs.
If I didn't answer your question correctly, maybe provide me with a bit more info ;)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Great article.
How do you think when we deploy nodejs app on openshift?
As we know, we can configure the CPU size and scale up the services.
Is this will increase apps performance with UV_THREADPOOL_SIZE config ?
Hi Akhmad. Thanks for the comment 👍.
So, with my limited knowledge of OpenShift, when you re-configure your CPU size, your node app doesn't get restarted and remains in memory. Therefore, it will not take advantage of the new CPU cores until it's rebooted.
However, if you autoscale your node services in that OpenShift spawns new replicas, then the new replicas will take advantages of the new CPUs.
If I didn't answer your question correctly, maybe provide me with a bit more info ;)