-
Notifications
You must be signed in to change notification settings - Fork 2
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
longer-term archival of results #68
Comments
here's a cool idea: making it really easy for someone to set up their own webserver running just the interactive component of this, so they could include it as a webpage with a publication. or, another way we could accomplish this: allow posting a link to an archive file (a la #67) available online; our server could download that archive and display the interactive results. Then we don't have to store them, but they can still publish an interactive viewer. |
I'd be interested to know how large 1000 result caches would be, for long-term storage. A few GB? |
well the 224 we have now are 181MB. So 1000 ought to be under 2GB. |
Great. So I see no reason to purge them if we don't need/have to. We could store them locally, or we could even throw them up into S3, if you wanted. |
Until there are 1,000,000 of them 😄 |
ha! Bring it on!! |
sounds like archival wouldn't create any real headaches. to make it even more manageable, you could by default delete all results on your server periodically (or whichever way you do it right now) and keep only those were the user pressed a "save" button on the results page |
Feature suggestion by @fhalbritter
The text was updated successfully, but these errors were encountered: