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

Update provisioning in units not just percentage #22

Closed
fwachsmuth opened this Issue Apr 10, 2013 · 4 comments

Comments

Projects
None yet
2 participants
@fwachsmuth

fwachsmuth commented Apr 10, 2013

For some table's access patterns, scaling the table in percent does not make sense and scaling by fixed amounts would make more sense.

Growth of table traffic isn't always exponential but can also be linear.

@sebdah

This comment has been minimized.

Owner

sebdah commented Apr 10, 2013

Thanks, this is a thing I've been having in the back of my head, but I haven't seen the use for it myself. Good to know that your use case needs it. Added it to the feature request pool.

@fwachsmuth

This comment has been minimized.

fwachsmuth commented Apr 10, 2013

What might make even more sense: Upscale by required amount (or a percentage of that). E.g. if consumed reads are 140% (you know dynamodb allows some grace bursts since a while) upscale by 40% (or 50% of that -- thus 20%)

@sebdah

This comment has been minimized.

Owner

sebdah commented Apr 17, 2013

A quick update. The code refactoring made prior to the 1.0.0 release has been made with this feature request in mind. Will have a look later on to see how to implement this best.

@sebdah

This comment has been minimized.

Owner

sebdah commented Apr 17, 2013

This feature has been fixed in version 1.1.0. Four new properties has been added:

  • increase-reads-unit
  • decrease-reads-unit
  • increase-writes-unit
  • decrease-writes-unit

All of those options takes either percent or units. If it is set to units Dynamic DynamoDB will scale up/down in units rather than percent.

No support for sensing buffer usage for now, unfortunately.

@sebdah sebdah closed this Apr 17, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment