[
https://issues.apache.org/jira/browse/RATIS-1924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Song Ziyang resolved RATIS-1924.
--------------------------------
Fix Version/s: 3.0.0
Resolution: Fixed
The PR is now merged. Thanks [~szetszwo] for working on this!
> Increase the default of raft.server.log.segment.size.max
> --------------------------------------------------------
>
> Key: RATIS-1924
> URL: https://issues.apache.org/jira/browse/RATIS-1924
> Project: Ratis
> Issue Type: Improvement
> Components: server
> Reporter: Tsz-wo Sze
> Assignee: Tsz-wo Sze
> Priority: Major
> Fix For: 3.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently, the default is 8MB which is very small. The servers will roll the
> log frequently and create a lot of small files.
> According to [~William Song]'s
> [comment|https://github.com/apache/ratis/pull/953#discussion_r1376972528],
> 32MB seems a good choice.
> {quote}
> It's only that I did experiments earlier and found 32MB is the optimal for
> IOTDB default workload. The experiments show:
> - (end to end throughput) improves substantially as segmented size grow from
> 8MB to 32MB, slowly from 32MB to 128MB.
> - The memory usage in JVM young increases as the segmented size grow, even if
> we restricted the max-cached-size and max-cached-segments. It turned out to
> be the open segment.
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
