[
https://issues.apache.org/jira/browse/IGNITE-10295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Voronkin updated IGNITE-10295:
------------------------------------
Description:
[16:33:34,410][INFO][sys-#122][GridDhtPartitionsExchangeFuture] Sending Full
Message performed in 0 ms.
[16:33:34,410][INFO][sys-#122][GridDhtPartitionsExchangeFuture] Sending Full
Message to all nodes performed in 0 ms.
[16:33:32,993][INFO][exchange-worker-#66][GridDhtPartitionsExchangeFuture]
Sending Single Message performed in 150 ms.
For varying number of caches, server nodes or number of partitions, reported
single message time change respectively, but reported full message time always
printed as 0 or 1 ms. Seems that it is calculated incorrectly, cause of async
send of message.
The most we spend in this method is actually open connection on send()
> Rework Sending Full Message logging.
> ------------------------------------
>
> Key: IGNITE-10295
> URL: https://issues.apache.org/jira/browse/IGNITE-10295
> Project: Ignite
> Issue Type: Improvement
> Reporter: Pavel Voronkin
> Priority: Major
>
> [16:33:34,410][INFO][sys-#122][GridDhtPartitionsExchangeFuture] Sending Full
> Message performed in 0 ms.
> [16:33:34,410][INFO][sys-#122][GridDhtPartitionsExchangeFuture] Sending Full
> Message to all nodes performed in 0 ms.
> [16:33:32,993][INFO][exchange-worker-#66][GridDhtPartitionsExchangeFuture]
> Sending Single Message performed in 150 ms.
>
> For varying number of caches, server nodes or number of partitions, reported
> single message time change respectively, but reported full message time
> always printed as 0 or 1 ms. Seems that it is calculated incorrectly, cause
> of async send of message.
> The most we spend in this method is actually open connection on send()
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
