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
Current rate limiter is based on single concurrent request per Range. Further customization of that limiter is desirable to achieve greater performance.
The text was updated successfully, but these errors were encountered:
Currently only client side buffering is serial per key-range, where as processing the batch is parallel.
And the serial part doesn't include T -> Stream conversion which is a significant part. With-out it its worth validating the requirements once.
What is not yet clear is if we want a Rate limiting based on RU/s (which would need to be across all key-ranges) or at the request-per-key-range level.
Ref #585
Current rate limiter is based on single concurrent request per Range. Further customization of that limiter is desirable to achieve greater performance.
The text was updated successfully, but these errors were encountered: