You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladislav Pyatkov (Jira)" <ji...@apache.org> on 2024/08/09 13:57:00 UTC
[jira] [Assigned] (IGNITE-22838) Operation returns to partition pool after it is handled in RAFT
[ https://issues.apache.org/jira/browse/IGNITE-22838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladislav Pyatkov reassigned IGNITE-22838:
------------------------------------------
Assignee: Vladislav Pyatkov
> Operation returns to partition pool after it is handled in RAFT
> ---------------------------------------------------------------
>
> Key: IGNITE-22838
> URL: https://issues.apache.org/jira/browse/IGNITE-22838
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vladislav Pyatkov
> Assignee: Vladislav Pyatkov
> Priority: Major
> Labels: ignite-3
>
> h3. Motivation
> After executing the synchronous embedded insert operation, we are returning to the partition-operations pool to return control to the client pool. We are just losing several microseconds instead of returning to the client pool directly.
> {noformat}
> finishFullTx:%node_3344%partition-operations-2 1.3 5476200 5477500
> Here is hidden 5.5 us
> kvPutEndMark:org.apache.ignite.internal.benchmark.InsertBenchmark.kvInsert-jmh-worker-1 0.0 5483000 5483000
> {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)