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
Warm lambdas are charged differently. Since we charge BOBA for Turing per call, it might be worth thinking about allowing alternative ways to charge Turing calls, since occasional calls won't make up for the real AWS costs.
AWS lambdas usually cool-down after a certain period of time.
That would be an issue for most production-grade use cases since the first Turing-Request would fail which then results in a failed transaction.
AWS supports something called "Provisioned concurrency" that basically keeps your Lambda warm.
Please note that enabling this option will result in increased fees the service, since warm lambdas are hourly charged instead of by calls.
You can read more about provisioned concurrency here.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Warm lambdas are charged differently. Since we charge BOBA for Turing per call, it might be worth thinking about allowing alternative ways to charge Turing calls, since occasional calls won't make up for the real AWS costs.
AWS lambdas usually cool-down after a certain period of time.
That would be an issue for most production-grade use cases since the first Turing-Request would fail which then results in a failed transaction.
AWS supports something called "Provisioned concurrency" that basically keeps your Lambda warm.
Please note that enabling this option will result in increased fees the service, since warm lambdas are hourly charged instead of by calls.
You can read more about provisioned concurrency here.
Beta Was this translation helpful? Give feedback.
All reactions