mirror of
https://github.com/openai/CLIP.git
synced 2026-11-05 01:37:26 +00:00
[GH-ISSUE #88] CUDA out of memory when running the training code on ubuntu 18.04 LTS #79
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
openai/CLIP#79
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @lycutter on GitHub (Apr 9, 2021).
Original GitHub issue: https://github.com/openai/CLIP/issues/88
When I re-train the clip network on Windows, it works well. But I re-train it on unbuntu, it always reminds me of CUDA out of memory no matter how I set the batch size. The configuration information of Windows and ubuntu are showed as follows:
Windows:
Ubuntu:
Besides, other pytorch projects work well on the Ubuntu. So I think the graphic card also works well and the memory is also sufficient. I try to update the pytorch version to 1.8, but it seems that it only support the version 1.7.1.
@vinson2233 commented on GitHub (Apr 9, 2021):
Can you share your training code?
Have you look the CUDA memory when loading the data, loading the model and doing a single forward?
@lycutter commented on GitHub (Apr 9, 2021):
Hello, my training code can be available at https://github.com/lycutter/CLIP/tree/master.
When I ran forward step on ubuntu, the allocated memory of graphic card didn't change.
@dragen1860 commented on GitHub (Apr 13, 2021):
@lycutter Hi, do you have multiple GPUs on ubuntu. YOu may need to block other GPUs in case of full GPU used.
@jongwook commented on GitHub (Apr 13, 2021):
Try memory profiling using pytorch_memlab to identify which operation causes the highest memory jump, and since you have the Windows version working, comparing the profiling results on Windows vs Linux would help. Setting environment variable
CUDA_LAUNCH_BLOCKING=1will also help getting more accurate profiling.@lycutter commented on GitHub (Apr 14, 2021):
It works, thanks you!