Skip to content
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_mem not correlated with task manager GPU memory usage #13275

Closed
1 task done
aqmery opened this issue May 31, 2024 · 3 comments
Closed
1 task done

GPU_mem not correlated with task manager GPU memory usage #13275

aqmery opened this issue May 31, 2024 · 3 comments
Labels
question Further information is requested

Comments

@aqmery
Copy link

aqmery commented May 31, 2024

Search before asking

Question

I've been using yolov8 for about a year now for this project, but for some reason something changed in the last week, where the GPU_mem on my training pc is not correlating anymore with the GPU memory usage in task manager.
I also keep getting message about pylace crashing, however, using some lighter settings I can train on my laptop with no issues and no obvious difference between GPU_mem and task manager GPU memory.
I don't really have a clue where to start debugging this, does anyone have any suggestions?

image (3)
image (4)
image (5)

Additional

No response

@aqmery aqmery added the question Further information is requested label May 31, 2024
@aqmery
Copy link
Author

aqmery commented May 31, 2024

Also it doesn't look like a memory leak issue, as the memory spikes this high basically from the start of the training loop and never goes down or much higher. (and training does take a lot longer, which would make sense if it's using the shared GPU memory, just really confused about the numbers in the print-outs)

@aqmery
Copy link
Author

aqmery commented May 31, 2024

I don't exactly know why, but restarting everything and making a new environment has somehow fixed this issue, no idea what the exact cause was, but it's fixed.

@aqmery aqmery closed this as completed May 31, 2024
@glenn-jocher
Copy link
Member

Great to hear that restarting and setting up a new environment resolved the issue! Sometimes, a fresh setup can clear up underlying conflicts or settings that are hard to pinpoint. If you encounter any other issues or have more questions in the future, feel free to reach out. Happy training with YOLOv8! 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants