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
Hi,
We're running a Nuxt 3 application in Docker containers, and we are trying to make sure that the amount of CPU that we are allocating to each container is optimal. We assumed that we should not allocate more than one core to each of the containers, given NodeJS - in general - is single-threaded. However, when running top inside our containers, we found that there are multiple child tasks that have been spawned, suggesting that Nitro might be using worker threads and hence may able to utilise more than one core.
Would the team be able to confirm if this is the case?
Are there any recommended maximum CPU or memory allocations when running Nitro in Docker?
Thanks!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
We're running a Nuxt 3 application in Docker containers, and we are trying to make sure that the amount of CPU that we are allocating to each container is optimal. We assumed that we should not allocate more than one core to each of the containers, given NodeJS - in general - is single-threaded. However, when running
top
inside our containers, we found that there are multiple child tasks that have been spawned, suggesting that Nitro might be using worker threads and hence may able to utilise more than one core.Would the team be able to confirm if this is the case?
Are there any recommended maximum CPU or memory allocations when running Nitro in Docker?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions