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
{{ message }}
This repository has been archived by the owner on Nov 17, 2023. It is now read-only.
Currently, upon running large tensor tests (CPU specific), we see memory footprint that exceeds the available memory (where nightly tests are run - C5 instance with <150G)
Attempts made -
Despite calling nd.waitall and empty_cache(), memory footprint continues to grow gradually (as nosetests proceed 1 test after another). For reference this commit - c48f70f
TODO:
C API to release CPU memory (similar to ReleaseAll) @anirudh2290 pointed out
empty_cache() is a No Op for CPU context.
So, need to get correct implementation for CPU specific usecases.
Hey, this is the MXNet Label Bot.
Thank you for submitting the issue! I will try and suggest some labels so that the appropriate MXNet community members can help resolve it.
Here are my recommended label(s): Test
Currently, upon running large tensor tests (CPU specific), we see memory footprint that exceeds the available memory (where nightly tests are run - C5 instance with <150G)
Thus we see errors like
Attempts made -
Despite calling nd.waitall and empty_cache(), memory footprint continues to grow gradually (as nosetests proceed 1 test after another). For reference this commit -
c48f70f
TODO:
@anirudh2290 pointed out
empty_cache() is a No Op for CPU context.
So, need to get correct implementation for CPU specific usecases.
Large tensor tests are maintained here
https://github.com/apache/incubator-mxnet/blob/master/tests/nightly/test_large_array.py
https://github.com/apache/incubator-mxnet/blob/master/tests/nightly/test_large_vector.py
The text was updated successfully, but these errors were encountered: