[jira] [Updated] (IGNITE-21798) Add properties to configure number of RAFT threads
[ https://issues.apache.org/jira/browse/IGNITE-21798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-21798: --- Reviewer: Denis Chudov > Add properties to configure number of RAFT threads > -- > > Key: IGNITE-21798 > URL: https://issues.apache.org/jira/browse/IGNITE-21798 > Project: Ignite > Issue Type: Improvement >Reporter: Vladislav Pyatkov >Priority: Major > Labels: ignite-3 > > h3. Motivation > We always have to work to reduce the number of threads in the product. In > this case, we create a double CPU for each disruptor that is used in the > replication layer. This is a lot of threads, and it is redundant in most > cases. We have to create a property to regulate the number in a specific case. > h3. Implementation notes > * The default number of threads should stay the same until we don't have a > test that shows a more stable value. > * *raft.stripes* is a startup configuration property to configure the number > of stripes. > * *raft.logStripesCount* is a startup configuration property to configure > the number of threads that are used to write WAL. > * *raft.logYieldStrategy* is a startup configuration property to use the > Yield strategy for WAL writer threads. > h3. Definition of done > Prepare all the described system properties > The task also assumes a throughput test scenario description -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21798) Add properties to configure number of RAFT threads
[ https://issues.apache.org/jira/browse/IGNITE-21798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-21798: --- Description: h3. Motivation We always have to work to reduce the number of threads in the product. In this case, we create a double CPU for each disruptor that is used in the replication layer. This is a lot of threads, and it is redundant in most cases. We have to create a property to regulate the number in a specific case. h3. Implementation notes * The default number of threads should stay the same until we don't have a test that shows a more stable value. * *raft.stripes* is a startup configuration property to configure the number of stripes. * *raft.logStripesCount* is a startup configuration property to configure the number of threads that are used to write WAL. * *raft.logYieldStrategy* is a startup configuration property to use the Yield strategy for WAL writer threads. h3. Definition of done Prepare all the described system properties The task also assumes a throughput test scenario description was: h3. Motivation We always have to work to reduce the number of threads in the product. In this case, we create a double CPU for each disruptor that is used in the replication layer. This is a lot of threads, and it is redundant in most cases. We have to create a property to regulate the number in a specific case. h3. Implementation notes * The default number of threads should stay the same until we don't have a test that shows a more stable value. * IGNITE_RAFT_STRIPES is a system property to configure the number of stripes. * IGNITE_RAFT_LOG_STRIPES is a system property to configure the number of threads that are used to write WAL. * IGNITE_RAFT_LOG_YIELD_STRATEGY is a system property to use the Yield strategy for WAL writer threads. h3. Definition of done Prepare all the described system properties The task also assumes a throughput test scenario description > Add properties to configure number of RAFT threads > -- > > Key: IGNITE-21798 > URL: https://issues.apache.org/jira/browse/IGNITE-21798 > Project: Ignite > Issue Type: Improvement >Reporter: Vladislav Pyatkov >Priority: Major > Labels: ignite-3 > > h3. Motivation > We always have to work to reduce the number of threads in the product. In > this case, we create a double CPU for each disruptor that is used in the > replication layer. This is a lot of threads, and it is redundant in most > cases. We have to create a property to regulate the number in a specific case. > h3. Implementation notes > * The default number of threads should stay the same until we don't have a > test that shows a more stable value. > * *raft.stripes* is a startup configuration property to configure the number > of stripes. > * *raft.logStripesCount* is a startup configuration property to configure > the number of threads that are used to write WAL. > * *raft.logYieldStrategy* is a startup configuration property to use the > Yield strategy for WAL writer threads. > h3. Definition of done > Prepare all the described system properties > The task also assumes a throughput test scenario description -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21798) Add properties to configure number of RAFT threads
[ https://issues.apache.org/jira/browse/IGNITE-21798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-21798: --- Description: h3. Motivation We always have to work to reduce the number of threads in the product. In this case, we create a double CPU for each disruptor that is used in the replication layer. This is a lot of threads, and it is redundant in most cases. We have to create a property to regulate the number in a specific case. h3. Implementation notes * The default number of threads should stay the same until we don't have a test that shows a more stable value. * IGNITE_RAFT_STRIPES is a system property to configure the number of stripes. * IGNITE_RAFT_LOG_STRIPES is a system property to configure the number of threads that are used to write WAL. * IGNITE_RAFT_LOG_YIELD_STRATEGY is a system property to use the Yield strategy for WAL writer threads. h3. Definition of done Prepare all the described system properties The task also assumes a throughput test scenario description was: h3. Motivation We always have to work to reduce the number of threads in the product. In this case, we create a double CPU for each disruptor that is used in the replication layer. This is a lot of threads, and it is redundant in most cases. We have to create a property to regulate the number in a specific case. h3. Implementation notes * The default number of threads should stay the same until we don't have a test that shows a more stable value. * IGNITE_RAFT_STRIPES is a system property to configure the number of stripes. * IGNITE_RAFT_WAL_STRIPES is a system property to configure the number of threads that are used to write WAL. * IGNITE_RAFT_WAL_YIELD_STRATEGY is a system property to use the Yield strategy for WAL writer threads. h3. Definition of done Prepare all the described system properties The task also assumes a throughput test scenario description > Add properties to configure number of RAFT threads > -- > > Key: IGNITE-21798 > URL: https://issues.apache.org/jira/browse/IGNITE-21798 > Project: Ignite > Issue Type: Improvement >Reporter: Vladislav Pyatkov >Priority: Major > Labels: ignite-3 > > h3. Motivation > We always have to work to reduce the number of threads in the product. In > this case, we create a double CPU for each disruptor that is used in the > replication layer. This is a lot of threads, and it is redundant in most > cases. We have to create a property to regulate the number in a specific case. > h3. Implementation notes > * The default number of threads should stay the same until we don't have a > test that shows a more stable value. > * IGNITE_RAFT_STRIPES is a system property to configure the number of > stripes. > * IGNITE_RAFT_LOG_STRIPES is a system property to configure the number of > threads that are used to write WAL. > * IGNITE_RAFT_LOG_YIELD_STRATEGY is a system property to use the Yield > strategy for WAL writer threads. > h3. Definition of done > Prepare all the described system properties > The task also assumes a throughput test scenario description -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21798) Add properties to configure number of RAFT threads
[ https://issues.apache.org/jira/browse/IGNITE-21798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-21798: --- Description: h3. Motivation We always have to work to reduce the number of threads in the product. In this case, we create a double CPU for each disruptor that is used in the replication layer. This is a lot of threads, and it is redundant in most cases. We have to create a property to regulate the number in a specific case. h3. Implementation notes * The default number of threads should stay the same until we don't have a test that shows a more stable value. * IGNITE_RAFT_STRIPES is a system property to configure the number of stripes. * IGNITE_RAFT_WAL_STRIPES is a system property to configure the number of threads that are used to write WAL. * IGNITE_RAFT_WAL_YIELD_STRATEGY is a system property to use the Yield strategy for WAL writer threads. h3. Definition of done Prepare all the described system properties The task also assumes a throughput test scenario description was: h3. Motivation We always have to work to reduce the number of threads in the product. In this case, we create a double CPU for each disruptor that is used in the replication layer. This is a lot of threads, and it is redundant in most cases. We have to create a property to regulate the number in a specific case. h3. Implementation notes * The default number of threads should stay the same until we don't have a test that shows a more stable value. * IGNITE_RAFT_STRIPES is a system property to configure the number of stripes. * IGNITE_RAFT_WAL_STRIPES is a system property to configure the number of threads that are used to write WAL. * IGNITE_RAFT_WAL_YIELD_STRATEGY is a system property to use the Yield strategy for WAL writer threads. > Add properties to configure number of RAFT threads > -- > > Key: IGNITE-21798 > URL: https://issues.apache.org/jira/browse/IGNITE-21798 > Project: Ignite > Issue Type: Improvement >Reporter: Vladislav Pyatkov >Priority: Major > Labels: ignite-3 > > h3. Motivation > We always have to work to reduce the number of threads in the product. In > this case, we create a double CPU for each disruptor that is used in the > replication layer. This is a lot of threads, and it is redundant in most > cases. We have to create a property to regulate the number in a specific case. > h3. Implementation notes > * The default number of threads should stay the same until we don't have a > test that shows a more stable value. > * IGNITE_RAFT_STRIPES is a system property to configure the number of stripes. > * IGNITE_RAFT_WAL_STRIPES is a system property to configure the number of > threads that are used to write WAL. > * IGNITE_RAFT_WAL_YIELD_STRATEGY is a system property to use the Yield > strategy for WAL writer threads. > h3. Definition of done > Prepare all the described system properties > The task also assumes a throughput test scenario description -- This message was sent by Atlassian Jira (v8.20.10#820010)
