[
https://issues.apache.org/jira/browse/IGNITE-22542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Bessonov updated IGNITE-22542:
-----------------------------------
Description:
{{org.apache.ignite.internal.network.DefaultMessagingService#isSelf}} - if we
detect that we send a message to the local node, we handle it immediately in
the same thread, which could be very bed for throughput of the system.
"send"/"invoke" themselves appear to be slow as well, we should benchmark them.
We should remove instantiation of InetSocketAddress for sure, if it's possible,
it takes time to resolve it. Maybe we should create it unresolved or just cache
it like in Ignite 2.
was:
{{org.apache.ignite.internal.network.DefaultMessagingService#isSelf}} - if we
detect that we send a message to the local node, we handle it immediately in
the same thread, which could be very bed for throughput of the system.
"send"/"invoke" themselves appear to be slow as well, we should benchmark them.
> Synchronous message handling on local node
> ------------------------------------------
>
> Key: IGNITE-22542
> URL: https://issues.apache.org/jira/browse/IGNITE-22542
> Project: Ignite
> Issue Type: Bug
> Reporter: Ivan Bessonov
> Priority: Major
> Labels: ignite-3
>
> {{org.apache.ignite.internal.network.DefaultMessagingService#isSelf}} - if we
> detect that we send a message to the local node, we handle it immediately in
> the same thread, which could be very bed for throughput of the system.
> "send"/"invoke" themselves appear to be slow as well, we should benchmark
> them. We should remove instantiation of InetSocketAddress for sure, if it's
> possible, it takes time to resolve it. Maybe we should create it unresolved
> or just cache it like in Ignite 2.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
