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

PR#3 updated region retrieval rates to the wrong values #4

Open
jwm opened this issue Jan 25, 2016 · 4 comments
Open

PR#3 updated region retrieval rates to the wrong values #4

jwm opened this issue Jan 25, 2016 · 4 comments

Comments

@jwm
Copy link

jwm commented Jan 25, 2016

Hi, thanks for maintaining this calculator!

I noticed that the results I was getting didn't match the official AWS calculator (http://calculator.s3.amazonaws.com/), and it seems to come down to the retrieval rates.

It seems like e754741 updated them to the wrong values. The examples I see in the Amazon Glacier FAQ all use $0.01/GB. Try as I might, I couldn't seem to find the per-region prices for Glacier retrieval.

If I take this calculator's results and adjust them for the $0.01/GB retrieval rate (in us-east-1), my results line up with the official AWS calculator and with the rudimentary calculation shown by the Glacier "Data Retrieval Policy" screen in the AWS Management Console.

@karpach Are you sure that the retrieval rates in your PR are current?

@karpach
Copy link
Contributor

karpach commented Jan 25, 2016

I got my prices from the official amazon glacier page:

Prices per region screenshot

@jwm
Copy link
Author

jwm commented Jan 25, 2016

@karpach As an example, in your commit (e754741), you changed the retrieval pricing in regionRetrievalRate() for us-west-2 from $0.011 to 0.055. Based on your screenshot, that value should have remained unchanged.

@karpach
Copy link
Contributor

karpach commented Jan 25, 2016

You are right. Looks like number of the requests is not taken into account by this calculator. I'll submit a fix.

@jwm
Copy link
Author

jwm commented Jan 25, 2016

Thanks @karpach!

@jwm jwm changed the title PR#3 updated region retrieval rates to the wrong values? PR#3 updated region retrieval rates to the wrong values Feb 1, 2016
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