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

What to do with old topAnat result files? #182

Open
fbastian opened this issue May 26, 2020 · 3 comments
Open

What to do with old topAnat result files? #182

fbastian opened this issue May 26, 2020 · 3 comments
Assignees
Labels

Comments

@fbastian
Copy link
Member

In GitLab by @smoretti on Feb 20, 2018, 09:57

What to do with old topAnat result files @fbastian & @marcrr ?

Today (Feb 20, 2018) those files occupy 95GB on disk and this will continue to increase.

Should we:

  • Delete some results after a while?
  • Store them compressed (this is not the case currently for most of them)
  • Reduce redundancy (the zip file we store contains tsv, pdf, R script, log, ... files we also store)
@fbastian fbastian self-assigned this May 26, 2020
@fbastian
Copy link
Member Author

In GitLab by @fbastian on Feb 20, 2018, 11:07

95 GB in more than 2 years of existence of TopAnat is not a concern IMO. We have the disk space to keep storing them, so just let's keep them untouched.

@fbastian
Copy link
Member Author

In GitLab by @marcrr on Feb 20, 2018, 11:32

From the discussion with @smoretti @vrechdelaval @jwollbrett , I would suggest the following:

  • include the release number in the hash, to allow more flexible solutions in the future.

  • consider storing only zip files, in all cases or after a while (1 month?)

@fbastian
Copy link
Member Author

In GitLab by @fbastian on Feb 20, 2018, 14:41

  • Files are stored in a different directory per version, so I don't think it is necessary to add the version in the hash. Plus it makes URL links portable between releases. Why would you like to add it? From what @vrechdelaval tells me, it's to be able to link to a specific release? It's not managed in the hash, but in the URL directly.

  • If we store only zip files, then we would need to modify the code to unzip it for displaying the results. But it's true that it would save lots of space.

I think there is no rush for now, as we don't have any problem yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant