[
https://issues.apache.org/jira/browse/IGNITE-24415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-24415:
---------------------------------------
Description:
In NamedNioEventLoopGroup, we don't pass thread count explicitly, so a Netty
default is used (cpus * 2, if not defined in a Java system property).
We should make this configurable via configuration.
We currently have 3 event loop groups: srv-accept, srv-worker, client (after
IGNITE-24411 'client' might be removed). We could either introduce a common
configuration for all of them, or configure them individually.
was:
In NamedNioEventLoopGroup, we don't pass thread count explicitly, so a Netty
default is used (cpus * 2, if not defined in a Java system property).
We should make this configurable via configuration.
We currently have 3 event loop groups: srv-accept, srv-worker, client (after
> Make Netty thread pools configurable
> ------------------------------------
>
> Key: IGNITE-24415
> URL: https://issues.apache.org/jira/browse/IGNITE-24415
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
>
> In NamedNioEventLoopGroup, we don't pass thread count explicitly, so a Netty
> default is used (cpus * 2, if not defined in a Java system property).
> We should make this configurable via configuration.
> We currently have 3 event loop groups: srv-accept, srv-worker, client (after
> IGNITE-24411 'client' might be removed). We could either introduce a common
> configuration for all of them, or configure them individually.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
