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
Currently we use grpc stream to send batch commands requests. The grpc send operations just put the encoded dataframe to the internal buffer and return quickly (there is a seperate loopyWriter goroutine for flushing the buffered data). Thus it's seldom for the kv client to batch more than 1 request, the average batch size of kv requests is typically 1.1 ~ 1.2 even for a high throughput workload like sysbench oltp point select. Besides, we can only batch more requests when the tikv is detected as overload, this is also a rare event and it's disabled by default. The batch efficiency can be improved for these high throughput workloads to reduce the overhead of grpc and syscalls.
The text was updated successfully, but these errors were encountered:
Enhancement
Currently we use grpc stream to send batch commands requests. The grpc send operations just put the encoded dataframe to the internal buffer and return quickly (there is a seperate
loopyWriter
goroutine for flushing the buffered data). Thus it's seldom for the kv client to batch more than 1 request, the average batch size of kv requests is typically 1.1 ~ 1.2 even for a high throughput workload like sysbench oltp point select. Besides, we can only batch more requests when the tikv is detected as overload, this is also a rare event and it's disabled by default. The batch efficiency can be improved for these high throughput workloads to reduce the overhead of grpc and syscalls.The text was updated successfully, but these errors were encountered: