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

Information and control over memory use #128

Open
jdries opened this issue Mar 21, 2024 · 2 comments
Open

Information and control over memory use #128

jdries opened this issue Mar 21, 2024 · 2 comments

Comments

@jdries
Copy link

jdries commented Mar 21, 2024

I'm trying to get more insight into memory use by GDAL:

For things like getting cache usage, I'm wondering if this can or should be done via standard binding?

@jamesmcclain
Copy link
Member

Hello,

Thanks so much for your interest. I am the author of the code in question (management of datasets), though @pomadchin may wish to chime in, as well. My understanding of the second half of your query is "is it possible for me to forcibly close open GDAL datasets"? It is not possible to do so selectively (to the best of my memory!), but you can use clear to close all of the datasets associated with the gdal-warp-bindings cache, which should in turn release GDAL resources. A more selective approach would indeed need a PR.

@pomadchin
Copy link
Member

:hmm: I think clear is not exposed via Java API 🤔 we could expose it. Dangerously can be used probably.

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

No branches or pull requests

3 participants