[
https://issues.apache.org/jira/browse/IGNITE-22838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladislav Pyatkov updated IGNITE-22838:
---------------------------------------
Description:
h3. Motivation
After executing the synchronous embedded insert operation, we are returning to
the partition pool to return control to the client pool. We are just losing
several microseconds instead of returning to the clietn pool directly.
{noformat}
RaftNodeOnEvent:%node_3344%JRaft-NodeImpl-Disruptor_stripe_2-0 0.0 5421700
5421700
Here is hidden 2.8 us
LogManagerOnEvent:%node_3344%JRaft-LogManager-Disruptor_stripe_2-0 0.1 5424500
5424600
{noformat}
h3. Definition of done
We need to develop a strategy that does not involve the extra thread in
synchronous operation.
was:
h3. Motivation
After executing the synchronous insert operation, we are returning to the
partition pool to return control to the client pool. We just lost several
microsseconds
> Operation returns to partition pool after it is handled in ARFT
> ---------------------------------------------------------------
>
> Key: IGNITE-22838
> URL: https://issues.apache.org/jira/browse/IGNITE-22838
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vladislav Pyatkov
> Priority: Major
> Labels: ignite-3
>
> h3. Motivation
> After executing the synchronous embedded insert operation, we are returning
> to the partition pool to return control to the client pool. We are just
> losing several microseconds instead of returning to the clietn pool directly.
> {noformat}
> RaftNodeOnEvent:%node_3344%JRaft-NodeImpl-Disruptor_stripe_2-0 0.0 5421700
> 5421700
> Here is hidden 2.8 us
> LogManagerOnEvent:%node_3344%JRaft-LogManager-Disruptor_stripe_2-0 0.1
> 5424500 5424600
> {noformat}
> h3. Definition of done
> We need to develop a strategy that does not involve the extra thread in
> synchronous operation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
