You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mxnet.apache.org by GitBox <gi...@apache.org> on 2018/01/18 06:50:39 UTC

[GitHub] weishy-xun opened a new issue #9474: how to release gpu memory in the garbage pool?

weishy-xun opened a new issue #9474: how to release gpu memory in the garbage pool?
URL: https://github.com/apache/incubator-mxnet/issues/9474
 
 
   As I can searched,  there're a lot of issues about gpu memory leaking, and always end with something like:
   
   > Memory isn't really 'leaked'. It's released to a pool. The pool will only be emptied when an allocation returns out of memory.
   
   However, when I use multiprocessing,  it is really painful,  because the "pool" isn't share between process. E.g. I have 4 processes, one ocuupied 11g, when another process get "out of memory", it cannot release the first process's garbage pool. And if I do not call the first process forever, the garbage will be there forever. Is there any method to release memory manually? Or can I set a memory limitation for a process?

----------------------------------------------------------------
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