smengcl commented on PR #6705: URL: https://github.com/apache/ozone/pull/6705#issuecomment-2123598233
> @jojochuang why not make this the default behavior for reads on client side? @kerneltime I want to take a different angle. -- I wonder where the overhead is coming from in the first place. In the case of Ratis, `XceiverClientRatis` itself does not appear to have much synchronization overhead. So I did a little bit of digging. And I think the limiting factor can be this config in each `RaftClient`: ``` raft.client.async.outstanding-requests.max ``` by default **each** `RaftClient` allows 100 outstanding requests. As a result only 100 parallel `RaftClient#send` can be in-flight at one point: https://github.com/apache/ratis/blob/release-3.0.1/ratis-client/src/main/java/org/apache/ratis/client/impl/OrderedAsync.java#L160-L183 We should try setting `raft.client.async.outstanding-requests.max` to 100000 and see what happens. cc @jojochuang @szetszwo -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
