Content-Length: 231763 | pFad | http://github.com/postgresml/postgresml/issues/1646

DF issue with SELECT pgml.clear_gpu_cache(); · Issue #1646 · postgresml/postgresml · GitHub
Skip to content

issue with SELECT pgml.clear_gpu_cache(); #1646

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

Open
leesean5150 opened this issue Oct 21, 2024 · 1 comment
Open

issue with SELECT pgml.clear_gpu_cache(); #1646

leesean5150 opened this issue Oct 21, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@leesean5150
Copy link

hi,

running:

psql -d postgresml
SELECT pgml.clear_gpu_cache();

doesnt seem to reduce my gpu usage. currently running a local docker container that is built from https://github.com/postgresml/postgresml/tree/9303cb4b68fe20b3667adeee96e25f5046b71a64/docker.

in an attempt to debug i installed pip, torch and numpy in the container, because i couldnt import torch in the python3 shell.
when running

print(f"Allocated memory: {torch.cuda.memory_allocated() / 1024**2:.2f} MB")
print(f"Allocated memory: {torch.cuda.reserved() / 1024**2:.2f} MB")

i got 0 for both print statements, but if i run

torch.randn(1024, 1024, device='cuda')

before the print statements i have a non-zero output.

for context, i am using korvus pipelines and collections for my models, and i am trying to reduce the amount of gpu resources being hogged, because the only way i have been able to reduce gpu consumption each time has been by restarting the postgresml container, which is not ideal for an application. is this the wrong way of using the command or are there any workarounds for this? thank you.

@leesean5150
Copy link
Author

leesean5150 commented Oct 24, 2024

i tried running the embedding command directly in the postgresml container. runnning the embedding directly in the postgresml database,the gpu memory gets consumed (previously from ~3gb to ~5gb). when running the cache clearing command, there was no change in my gpu memory usage.

image

@SilasMarvin SilasMarvin added the bug Something isn't working label Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants








ApplySandwichStrip

pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier!      Saves Data!


--- a PPN by Garber Painting Akron. With Image Size Reduction included!

Fetched URL: http://github.com/postgresml/postgresml/issues/1646

Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy