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

Latency? #13

Open
scw opened this issue Jan 7, 2016 · 1 comment
Open

Latency? #13

scw opened this issue Jan 7, 2016 · 1 comment

Comments

@scw
Copy link

scw commented Jan 7, 2016

An attribute that is useful for comparison is the retrieval time for data. Because of the variance involved, it isn't possible to make precise claims, but it's still useful to know the order of magnitude (ms vs sec). For example, Glacier takes hours to restore, Google Nearline takes seconds, or milliseconds for S3.

@gaul
Copy link
Owner

gaul commented Jan 15, 2016

I like this idea but it is hard to compare across providers. Only Glacier seems to give a 3-5 hour SLA and I cannot find references for nearline. Basically anything that uses erasure encoding instead of replicas should be nearline on the order of seconds to minutes.

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

No branches or pull requests

2 participants