What would you like?
I would like to keep busy waiting and avoid suspension/replay overhead if the replay is going to happen soon, which includes the following scenarios:
- the next retry of a failed step operation
- next check of waitForCondition
- expiration of a wait operation
The busy waiting behavior should be customizable, by providing either
- a maximum busy wait period field in DurableConfig (default: 0, busy waiting is disabled), or
- a busy waiting strategy in DurableConfig, accepting Lambda's remaining invocation time and next replay time as parameters
Possible Implementation
No response
Is this a breaking change?
No
Does this require an RFC?
No
Additional Context
No response
What would you like?
I would like to keep busy waiting and avoid suspension/replay overhead if the replay is going to happen soon, which includes the following scenarios:
The busy waiting behavior should be customizable, by providing either
Possible Implementation
No response
Is this a breaking change?
No
Does this require an RFC?
No
Additional Context
No response