You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pegasus.apache.org by GitBox <gi...@apache.org> on 2021/07/30 09:52:34 UTC
[GitHub] [incubator-pegasus] Shuo-Jia edited a comment on issue #797: Feature enhancement: throttling by the count of kvs
Shuo-Jia edited a comment on issue #797:
URL: https://github.com/apache/incubator-pegasus/issues/797#issuecomment-889777941
> * If throttling by qps,one request may contain different size of data, it's hard to control the pressure.
> * If throttling by size, it's difficult for users to calculate the required quota, and it can't be used for read request.
- `throttling by qps` and `throttling by size` can be set at the same time
- the suggestion seem don't resolve the `read size throttling`
> The server will perform throttling according to the value of kv_count
The qps throttling is for `RPC`, but not `record count`. if the total size is permissible(for example, size is small, but the count is large), we should allow it, it's also say we don't care the `kv count` in this case. or if you want limit `large kv_count`, we support the feature in java client, which limit the count <= 1000
So I think you can set ` throttling by qps` and `throttling by size` at same time to resolve your problem
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@pegasus.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pegasus.apache.org
For additional commands, e-mail: dev-help@pegasus.apache.org