You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Model creation/verification can be expensive, and even run into throttling on CreateTable and DescribeTable with enough concurrent model binding. This is a potential issue now that AWS Lambda supports Python 3.6 and users may bind models in a lambda function that runs thousands of times.
An option(s) to skip DynamoDB calls during bind improves lambda setup and reduces the risk of throttling.
A few ideas:
Single flag named so that calling code is explicit about the disabled step: skip_table_setup=False or maybe local=False, or local_bind=False. Leaning towards local as a kwarg only so that it's concise but has to be explicitly specified: no ambiguous positional boolean eg. bind(MyModel, True).
Less preferred: individual options for fine-grained control skip_verify=False, skip_create=False
The text was updated successfully, but these errors were encountered:
Model creation/verification can be expensive, and even run into throttling on CreateTable and DescribeTable with enough concurrent model binding. This is a potential issue now that AWS Lambda supports Python 3.6 and users may bind models in a lambda function that runs thousands of times.
An option(s) to skip DynamoDB calls during bind improves lambda setup and reduces the risk of throttling.
A few ideas:
skip_table_setup=False
or maybelocal=False
, orlocal_bind=False
. Leaning towardslocal
as a kwarg only so that it's concise but has to be explicitly specified: no ambiguous positional boolean eg.bind(MyModel, True)
.skip_verify=False, skip_create=False
The text was updated successfully, but these errors were encountered: