-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GPU memory leak. #55
Comments
I haven't seen this in the past and don't currently have a GPU available for testing, unfortunately 😕 |
I "fixed" the problem. When I install pycave it forces an old installation of PyTorch (1.12) with the "torchkit" dependency. After that, I reinstall the latest 2.01 version of PyTorch and there are no more memory leaks! I can use the batch function normally!! |
@borchero Since my last message I noticed something, in the poetry.lock file you have this: [package.dependencies] Which I belive forces the install of the older version of PyTorch (1.12). |
Hello,
I'm using pycave for a project where the data is unidimensional of size 8e9. The GPU options works well, and I'm splitting the data in "for loops" to do the predictions. However, as the loops goes on, it takes more and more of the GPU memory, and eventually runs out of memory. To contour this issue, I'm using torch clean cache at each interaction in addition to the garbage collector function in python, as shown in the code below, however this process is slow.
I've tried to use the pycave built-in function of batches as well, but it also runs in the memory issue.
Is there anything I could do to fix this?
The text was updated successfully, but these errors were encountered: