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

Slow hash on large destination paths #11

Open
keybraker opened this issue Oct 4, 2024 · 0 comments
Open

Slow hash on large destination paths #11

keybraker opened this issue Oct 4, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@keybraker
Copy link
Owner

On the current solution, system goes through the entire destination path and hashes all the files in it. This means that for destination paths with a lot of files, it takes a lot of time and memory to hash all the images.
This is not only slow but not a good solution as well, as if only one image is to be moved the whole destination path is hashed for one image.

This should change and the hashing of a path should only happen when a destination path is decided for an image. This can also be cached in order to not have double hashing of same destination paths.

@keybraker keybraker added the enhancement New feature or request label Oct 4, 2024
@keybraker keybraker self-assigned this Oct 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant