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
The existing task polling is naive and doesn't consider the various edge cases around output length, polling algorithms, etc...
Modify the implementation to take advantage of the log appending support in the API.
Modify the polling algorithm to reduce server resource consumption (i.e., do polling client side instead of server side).
Check if there is a need for supporting more advanced polling algorithms (.e.g, backoff policies, etc).
The text was updated successfully, but these errors were encountered:
Another thought, following the observation on #183 (comment): Request with some reasonable wait amount for the first request, since if it is a quick task, it will return early. Then if longer than that, start polling.
The existing task polling is naive and doesn't consider the various edge cases around output length, polling algorithms, etc...
Modify the implementation to take advantage of the log appending support in the API.
Modify the polling algorithm to reduce server resource consumption (i.e., do polling client side instead of server side).
Check if there is a need for supporting more advanced polling algorithms (.e.g, backoff policies, etc).
The text was updated successfully, but these errors were encountered: