You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by GitBox <gi...@apache.org> on 2019/01/25 17:06:05 UTC

[GitHub] sven-lange-last commented on issue #104: Dynamically setting the memory limit of the Nodejs VM

sven-lange-last commented on issue #104: Dynamically setting the memory limit of the Nodejs VM
URL: https://github.com/apache/incubator-openwhisk-runtime-nodejs/pull/104#issuecomment-457643203
 
 
   @Liu-HongYe please have a look at https://github.com/apache/incubator-openwhisk/issues/3246 and https://github.com/apache/incubator-openwhisk/pull/4155. While the memory limit for a container restricts the resident size (physical memory) of the processes, Node.js setting `--max-old-space-size` very likely affects virtual memory usage - I could not find good detail information on this setting quickly.
   
   Setting `--max-old-space-size` to a value relative to the physical memory limit may not yield the expected results but restrict usable memory even more... Did you perform measurements / experiments on the effects?
   
   Which exact behaviour do you want to achieve with your change?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services