[
https://issues.apache.org/jira/browse/IGNITE-20373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Scherbakov updated IGNITE-20373:
---------------------------------------
Labels: ignite-3 ignite3_performance (was: )
> Fix IO threading model
> ----------------------
>
> Key: IGNITE-20373
> URL: https://issues.apache.org/jira/browse/IGNITE-20373
> Project: Ignite
> Issue Type: Improvement
> Affects Versions: 3.0
> Reporter: Alexey Scherbakov
> Priority: Major
> Labels: ignite-3, ignite3_performance
> Fix For: 3.0
>
>
> Currently IO is resubmitted to inbound pool for further processing (even
> there are corner cases then a message handler called in IO thread)
> It introduces additional latency in message processing because each component
> other uses it's own pools.
> addMessageHandler should be extended with a 3-d argument: a pool for
> submitting a callback for execution.
> Some kind of message header can be passed along the way for precise pool
> selection (similar to jraft IO model)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
