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
I've seen an era where sometimes the node process will run out of space on the heap. As long as those memory available this can be solved by using the command line parameter Max old space size.
In order to do the simplest change that will bring this ability to the binary as well as, the the npm global install versions, a rapper file that becomes the new launcher file for the application is a good idea. The wrapper file can then spawn a new node process with the correct come online arguments.
Also we want to set the max old space size to a value that depends on the memory available in the system. Say 80% of the available memory. We can compute this using shell script functions but they may not be portable across different platforms. So we can probably compute it using node internal functions and properties itself another reason why a wrapper launcher script to launch the actual application and set that come online parameter to an amount of memory that depends on the actual memory available to the system is a good idea.
The text was updated successfully, but these errors were encountered:
I've seen an era where sometimes the node process will run out of space on the heap. As long as those memory available this can be solved by using the command line parameter Max old space size.
In order to do the simplest change that will bring this ability to the binary as well as, the the npm global install versions, a rapper file that becomes the new launcher file for the application is a good idea. The wrapper file can then spawn a new node process with the correct come online arguments.
Also we want to set the max old space size to a value that depends on the memory available in the system. Say 80% of the available memory. We can compute this using shell script functions but they may not be portable across different platforms. So we can probably compute it using node internal functions and properties itself another reason why a wrapper launcher script to launch the actual application and set that come online parameter to an amount of memory that depends on the actual memory available to the system is a good idea.
The text was updated successfully, but these errors were encountered: