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

[Suggestions] Features for storage optimization #2837

Open
4 of 22 tasks
Tracked by #2959
Didayolo opened this issue Aug 25, 2020 · 1 comment
Open
4 of 22 tasks
Tracked by #2959

[Suggestions] Features for storage optimization #2837

Didayolo opened this issue Aug 25, 2020 · 1 comment
Labels
Enhancement For future features/suggestions and enhancements P1 Storage

Comments

@Didayolo
Copy link
Member

Didayolo commented Aug 25, 2020

Hard limits (bundle upload max size, submissions max size, duration of computation on default queue, etc.) should be configurable in the .env file in order to be adapted to each instances.

My Datasets

  • When a user delete a dataset from My Datasets page, erase it from storage (garbage collection, with retro-action)
  • Warn for unused datasets (e.g. display in red)
  • Button to delete all unused datasets
  • Max upload size for bundles and datasets (e.g. 10 GB)

Redundancy

  • Delete redundant files and add sym links (pointers)
    Users upload the same files many times: submissions, bundles, etc.
  • Can we erase ZIP archives after they got unzipped? (uploads directory)
  • Problem with files of size 0 Files size=0 in MinIO #3004
  • Remove uploads (zip files uploaded) after x months. These are the files that take up the most storage and have the least need to remain permanent.

Submissions

  • Button to erase all failed submissions
  • Button to erase all the submissions while keeping the latest 3 submissions per participant in each phase
  • Automatic purge of failed submissions?
  • Submissions should count in the storage quota, and users should have an interface to manage their submissions from all competitions and delete them.
  • Submission size limitation (edit menu): the default value is 0, which means "no limitation". We may want to put a reasonable value (e.g. 30 MB) to limit submissions by default. default max submission size of 300mb upon phase form initialisation #3052
  • Cool down before being able to re-submit
  • Max submission size (e.g. 2 GB to avoid 50 GB submissions...)

Others

  • Quota : impose a storage limitation to users (also for security reasons)
  • Monitoring tools
  • Glacial Storage? Glacial Storage #2836
  • Notification to admin when storage is low Docker HDD Space #2291
  • Limitation on the number of competitions allowed by user

Compute workers storage

@Didayolo Didayolo added Enhancement For future features/suggestions and enhancements future labels Aug 25, 2020
@Didayolo Didayolo removed the future label May 31, 2021
@dtuantran
Copy link
Collaborator

I'd like to add this issue #3004

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement For future features/suggestions and enhancements P1 Storage
Projects
None yet
Development

No branches or pull requests

2 participants