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

disk cache doesn't seem to work. #92

Open
chorongi opened this issue Oct 6, 2023 · 1 comment
Open

disk cache doesn't seem to work. #92

chorongi opened this issue Oct 6, 2023 · 1 comment

Comments

@chorongi
Copy link

chorongi commented Oct 6, 2023

Ran with
sudo -S -E geesefs -o allow_other --cache-to-disk-hits 0 --memory-limit 1000 --endpoint "$s3_endpoint" --file-mode=0444 --dir-mode=0777 "$bucket" "$bucket_path";

I have 2 quetsions.

  1. What is the --cache parameter used for? What happens if I don't specify this parameter? How do I make it cache on the mounted geesefs directory?

  2. By setting to --cache-to-disk-hits 0 I was expecting the cache any file on its first time read. Afterwards, I would expect the read operation of the file to be much faster since it will be stored on local disk, however the subsequent reads seem to be slow, and tries to fetch the file online from s3 again. What should I do to make geesefs do the behavior that I mentioned?

Thanks for developing such a useful tool!

@chorongi
Copy link
Author

chorongi commented Oct 6, 2023

I also tried

  1. specifying --cache parameter. Nothing seems to be stored in directory.
  2. decreasing --memory-limit 128. Nothing seems to be cached.

I am mounting a S3 bucket of images, and I expect images being used to be cached in local disk on first fly and accessed from local for subsequent read ops to get fast performance.

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

1 participant