[
https://issues.apache.org/jira/browse/RATIS-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17935765#comment-17935765
]
Tsz-wo Sze edited comment on RATIS-2259 at 3/15/25 6:16 PM:
------------------------------------------------------------
[~andywu], how many clients are there? Could you try benchmarking the server
(bypass the RaftClient, call the server methods directly)?
FYI, Apache Ozone has over 100k IOPS; see
https://medium.com/engineering-cloudera/ozone-performance-improvements-c0bb8a76dc94
was (Author: szetszwo):
[~andywu], how many clients are there? Could you try benchmarking the server
(bypass the RaftClient, call the server methods directly)?
Apache Ozone has over 100k IOPS; see
https://medium.com/engineering-cloudera/ozone-performance-improvements-c0bb8a76dc94
> Improve the read latency of RaftClient
> --------------------------------------
>
> Key: RATIS-2259
> URL: https://issues.apache.org/jira/browse/RATIS-2259
> Project: Ratis
> Issue Type: Improvement
> Components: client
> Reporter: Andy Wu
> Priority: Major
>
> Hey Folks,
> We are using ratis library to perform around ~2K/s read operations. Here is
> the API we are using:
> {code:java}
> RaftClient#sendReadOnlyAsync ==> it is OrderedAsync{code}
> I understand the above API is ordered, it will be filed sequentially. The
> read latency is keeping going up for each cid:
> e.g.
> duration: 15 ms, cid=2
> duration: 20 ms, cid=3
> …..
> duration: 100 ms, cid=100
> For the read operations, the order is not important to us. How do we improve
> the latency while keeping the throughput high? I tried *UnorderedAsync,* it
> has similar behaviors. Anything I missed?
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
