-
-
Notifications
You must be signed in to change notification settings - Fork 595
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
RESOURCE_EXHAUSTED
error when starting Mega_full
#78
Comments
Mega_full
(3080ti w/ 12GB)
Mega_full
(3080ti w/ 12GB)RESOURCE_EXHAUSTED
failure when starting Mega_full
RESOURCE_EXHAUSTED
failure when starting Mega_fullRESOURCE_EXHAUSTED
error when starting Mega_full
Got in a similar loop when trying to start the back-end using a 1050ti:
|
Are there any required/recommended GPU specs for the |
Currently running the |
Thanks @Aeriit. I assume it won’t be possible, but are you aware of any way to work around this since I’m “so close” to the VRAM requirements? |
Found a solution in my caseI solved my issue by setting a couple environment variables for python before starting the backend.
This document explains why those environment variables are helpful. I'm now able to run the backend natively using the Edit: I eventually had another |
@davisengeler, unfortunately, that doesn't help on WSL for me. |
I'm able to run Mega_Full on twin RTX 2080 TIs, each with 11 GB memory, and the NVIDIA library spreads the loading of the model across both GPUs until they are full. Image processing is spread across both GPUs too. |
Context
I’ve got the project running nicely when using
mini
andMega
models with an RTX 3080ti (12GB) on Ubuntu 22.03. Results take less than 4 seconds per image when usingMega
.Problem
Despite all other models working, I’ve not been able to start a
Mega_full
instance. I keep getting aRESOURCE_EXHAUSTED
error after starting the server (full traceback below). It’s possible this 12GB GPU simply isn’t enough, but I figured I’d report it here for feedback before dismissing it. Thanks for any recommendations!Full Traceback
The text was updated successfully, but these errors were encountered: