[
https://issues.apache.org/jira/browse/IGNITE-24484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17932420#comment-17932420
]
Vladislav Pyatkov edited comment on IGNITE-24484 at 3/5/25 3:08 PM:
--------------------------------------------------------------------
The branch where I tested it ignite-24484-benchmark
{code:java}
Benchmark (fsync) (replicaCount) (useHeartbeatCoalescing)
Mode Cnt Score Error Units
MultiTableBenchmark.test false 1 false
thrpt 20 52238.784 ± 2711.107 ops/s
MultiTableBenchmark.test false 1 true
thrpt 20 52083.244 ± 3323.483 ops/s
MultiTableBenchmark.test false 3 false
thrpt 20 21211.237 ± 1605.232 ops/s
MultiTableBenchmark.test false 3 true
thrpt 20 24562.209 ± 1645.234 ops/s
{code}
was (Author: v.pyatkov):
{code:java}
Benchmark (fsync) (replicaCount) (useHeartbeatCoalescing)
Mode Cnt Score Error Units
MultiTableBenchmark.test false 1 false
thrpt 20 52238.784 ± 2711.107 ops/s
MultiTableBenchmark.test false 1 true
thrpt 20 52083.244 ± 3323.483 ops/s
MultiTableBenchmark.test false 3 false
thrpt 20 21211.237 ± 1605.232 ops/s
MultiTableBenchmark.test false 3 true
thrpt 20 24562.209 ± 1645.234 ops/s
{code}
> RAFT heartbeat coalescing
> -------------------------
>
> Key: IGNITE-24484
> URL: https://issues.apache.org/jira/browse/IGNITE-24484
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vladislav Pyatkov
> Assignee: Vladislav Pyatkov
> Priority: Major
> Labels: ignite-3
> Attachments: MultiTableBenchmark.java
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> h3. Motivation
> RAFT heartbeat exists for any RAFT group. Even in the case several groups are
> deployed in the one node, the exchange group generates its own heartbeat
> message. This leads to a high load on the network layer and CPU.
> h3. Definition of done
> Heartbeat messages should be sent with a particular frequency for an Ignite
> node (independently of the number of RAFT groups).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
