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

fix: streamline cache exploration #135

Merged
merged 1 commit into from
Jul 8, 2022
Merged

Conversation

aduh95
Copy link
Contributor

@aduh95 aduh95 commented Jun 29, 2022

If a large number of versions are cached on the host system, trying to read the whole cache at once can be quite memory intensive. Instead, we can use an iterative approach that doesn't hold the whole directory content in memory.

If a large number of versions are cached on the host system, trying to
read the whole cache at once can be quite memory intensive. Instead, we
can use an iterative approach that doesn't hold the whole directory
content in memory.
Copy link
Contributor

@arcanis arcanis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks ok - do you have before/after numbers, for reference?

@aduh95
Copy link
Contributor Author

aduh95 commented Jul 8, 2022

Looks ok - do you have before/after numbers, for reference?

I don't have any, and tbh I would expect for it to only matter if the cache directory grows significantly on a memory limited system. But better safe than sorry, right?

@aduh95 aduh95 merged commit 185da44 into main Jul 8, 2022
@aduh95 aduh95 deleted the optimize-cache-exploration branch July 8, 2022 17:21
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

Successfully merging this pull request may close these issues.

2 participants