-
Notifications
You must be signed in to change notification settings - Fork 6
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
Result pagination #2
Comments
I presume you meant 10000 changed blocks and inaccurate results for any snapshot with changes exceeding ~5GB from the last snapshot. Were you able to finally reconcile your script generated numbers with AWS billing? |
Yes, likely that. I think I just went with the simple "works for volume < 5GB". I only used this to get estimates when using a new snapshot schedule. I never properly checked whether it matches the billing numbers, but it was close enough for my estimates. |
Corrections for Python 3.9 and based on Issue akirsman#2 at akirsman#2.
The current script only lists the first 10000 changed pages for each snapshot, so gives inaccurate results for any volume larger than around 5GB.
I changed the relevant part to this to use pagination:
There is probably a similar issue in listing the snapshots, but it's less likely to run into the limit there.
The text was updated successfully, but these errors were encountered: