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

Memory management #218

Open
PaulaPerezL opened this issue Jan 26, 2024 · 3 comments
Open

Memory management #218

PaulaPerezL opened this issue Jan 26, 2024 · 3 comments

Comments

@PaulaPerezL
Copy link

I have some troubles managing memory when reading and saving images. How do you handle it? Do you store each image in its own Zarr, or do you stack them up into one big Zarr?

Thank you very much

@peterdudfield
Copy link
Collaborator

peterdudfield commented Jan 26, 2024

We do a bit of both, for our production service we store each image as its own zarr, and then we join then together to make a joint zarr. We seperate non hrv and hrv out.

We run the service on AWS using these memory limits - https://github.com/openclimatefix/ocf-infrastructure/blob/main/terraform/modules/services/sat/ecs.tf#L4

What memory limits did you have?

@jacobbieker should we put some of this in the readme? We could add it to the https://github.com/openclimatefix/Satip?tab=readme-ov-file#running-in-production section.

@peterdudfield
Copy link
Collaborator

Does this make sense @PaulaPerezL ?

@PaulaPerezL
Copy link
Author

Yes, thank you, it makes sense. What happened to us is that the command "del object" is not working, or at least it does not release the RAM consumed by that object. However, we devised a method to launch each image in an independent process, and by doing so, we are able to clear the RAM after reading the image.

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

2 participants