-
Notifications
You must be signed in to change notification settings - Fork 16
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
feat: add CSV votes cleanup strategy #80
Comments
I think it is ok to keep this cache 🙈 @bonustrack what do you think? would it be costly? |
I didn't try before, but maybe something like the expiry date will help this case (if we need this) https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/S3.html#putBucketLifecycle-property |
I think there is no api currently returning the bucket size. Only way is to consult the admin panel. We do not have analytics, but I believe that old proposals are forgotten forever, there is no need to keep it’s cache. In the worst case, user can trigger the cache again. Setting expiry is a possibility, will look into it |
If expiry doesn't work, another idea is to have subdirectories with auto incremental numbers for every six months |
This one is expiring the whole bucket, there seems to be no way to expire files individually. Subdirectory method works only if we expire by creation time, but this is not the case, we expire also by last access date, in addition of creation time. |
Yea we can just delete files once in a while if it is adding lot of cost, |
Votes CSV reports will grow in count and size over time, and will increase the AWS storage cost.
We should have a prune strategy, which remove old and files that were not accessed for some time. In case someone request them again, they can trigger the cache creation and download them again.
A very basic strategy:
The text was updated successfully, but these errors were encountered: