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

Make the raw API serve zipped data #453

Open
bepetersn opened this issue Jul 5, 2014 · 2 comments
Open

Make the raw API serve zipped data #453

bepetersn opened this issue Jul 5, 2014 · 2 comments
Labels

Comments

@bepetersn
Copy link
Member

As it is currently, we take up a lot of space (~4 MB) each day with unzipped copies of the results of a scrape. We were considering making it zipped data before @nwinklareth left, if I am recalling correctly. Or am I wrong?

@nwinklareth
Copy link
Contributor

Storing 10 years of snapshots will take up 65% or so of the remaining 31G
of free disk space, so it is not that pressing of a concern.

Upon reflection I think that the snapshots should be moved to Amazon S3
drive, this would minimize the storage and delivery cost for that data.

Norbert

On Sat, Jul 5, 2014 at 1:52 PM, Brian Everett Peterson <
notifications@github.com> wrote:

As it is currently, we take up a lot of space (~4 MB) each day with
unzipped copies of the results of a scrape. We were considering making it
zipped data before Norbert left, I just remembered.


Reply to this email directly or view it on GitHub
#453.

Regards

Norbert

Norbert Winklareth

@bepetersn
Copy link
Member Author

Hey, that's a good idea. Because money required for hosting IS a concern where space is not so much, as you point out. Should I make that a future issue?

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

2 participants