kitex-双向stream中的发送延迟是否有调优的参数
- Dominant language
- Go
- Stars
- 8k
- Forks
- 918
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 7
Description
目前发现使用kitex的bidirection-stream来做低延迟的包发送,发现stream.Send之后,对端的stream.Recv有400us的延迟
现在调节 server.WithGRPCReadBufferSize,server.WithGRPCWriteBufferSize的大小好像没有什么用
目前不大清楚kitex的网络层是否还有类似缓冲区大小BufferSize和flush的interval的流控参数,对于大容量低延迟场景有啥更多的控制参数暴露出来?
另外kitex有没有基于stream中的msg的send和recv延迟的内置的监控指标?
Contributor guide
Research direction
Start with the bidirectional-stream entry points stream.Send, stream.Recv, and the server.WithGRPCReadBufferSize and server.WithGRPCWriteBufferSize options. Trace how buffering and flushing are handled, then check whether stream message send/receive latency metrics already exist. Done means the available tuning controls and monitoring support are identified or clearly scoped for exposure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, grpc
- Domain
- api, backend, observability, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100