You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ratis.apache.org by "Song Ziyang (Jira)" <ji...@apache.org> on 2022/10/25 18:12:00 UTC

[jira] [Created] (RATIS-1730) Use Daemon thread to evict RaftLogCache

Song Ziyang created RATIS-1730:
----------------------------------

             Summary: Use Daemon thread to evict RaftLogCache
                 Key: RATIS-1730
                 URL: https://issues.apache.org/jira/browse/RATIS-1730
             Project: Ratis
          Issue Type: Improvement
            Reporter: Song Ziyang
            Assignee: Song Ziyang


Using JProfiler, I found almost 50% of AppendEntriesAsync execution time is spent on checkAndEvictCache, see the attached pic. There's also a TODO[1] suggesting to use a daemon thread to perform checkAndEvictCache. 

Here are my configurations:

RaftLog SegmentSize: 96MB

RaftLogCache Segment Num Max: 2

RaftLogCache Size Max: 200MB

 

Am I setting the configurations improperly? If not, we shall use a daemon thread.

 

[1]https://github.com/apache/ratis/blob/b8117f41481f5f5861566a68bb1ea4dc7c60320c/ratis-server/src/main/java/org/apache/ratis/server/raftlog/segmented/SegmentedRaftLog.java#L402



--
This message was sent by Atlassian Jira
(v8.20.10#820010)