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
Hey there, thanks for creating this project, it's really cool and extremely helpful.
We're trying to use nexe to bundle some of our tools and we're running into an issue when using it inside a container: the container runs out of memory due to the number of processes spawned (the host machine has 72 cores).
As you can see in nodejs/node#28765 and nodejs/node#28855, node's os.cpus doesn't really query the correct location on Linux and therefore can't get the number of available CPUs, so even though we're actually running the container with only 2 cores, nexe/resolve-dependencies still assumes 72 cores are available.
Would you be open to introducing an option in nexe and resolve-dependencies to limit the number of children spawned by the dependency resolution process? Or perhaps use a namespace-aware library for querying the number of available CPUs?
Thanks!
The text was updated successfully, but these errors were encountered:
Hey there, thanks for creating this project, it's really cool and extremely helpful.
We're trying to use nexe to bundle some of our tools and we're running into an issue when using it inside a container: the container runs out of memory due to the number of processes spawned (the host machine has 72 cores).
As you can see in nodejs/node#28765 and nodejs/node#28855, node's os.cpus doesn't really query the correct location on Linux and therefore can't get the number of available CPUs, so even though we're actually running the container with only 2 cores, nexe/resolve-dependencies still assumes 72 cores are available.
Would you be open to introducing an option in nexe and resolve-dependencies to limit the number of children spawned by the dependency resolution process? Or perhaps use a namespace-aware library for querying the number of available CPUs?
Thanks!
The text was updated successfully, but these errors were encountered: