[IGNITE-23641] Fast switching thread for thin client batch operation

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Labels: ignite-3
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Unassigned
• Reporter: Vladislav Pyatkov
• Created: 08/Nov/24 15:29
• Updated: 27/Nov/24 07:18

Description

Motivation

We have already done it for other table operations IGNITE-23616, but we could not do that for batch one.
The reason why we excluded the batch operation is a performance penalty in the latency benchmark. Because if the thread is an early switch to a `partitons-operation` thread, we won't switch the thread further:

// If the request actually came from the network, we are already in the correct thread that has permissions to do storage reads
// and writes.
// But if this is a local call (in the same Ignite instance), we might still be in a thread that does not have those permissions.
if (shouldSwitchToRequestsExecutor(STORAGE_READ, STORAGE_WRITE, TX_STATE_STORAGE_ACCESS)) {
    requestsExecutor.execute(() -> handleReplicaRequest(request, sender, correlationId));
} else {
    handleReplicaRequest(request, sender, correlationId);
}

As a result, the batch operation is executed in the single thread. But before we had a possibility to choose a dedicated thread for each partiton.

InternalTableImpl#enlistInTx(Collection, InternalTransaction, IgnitePentaFunction, Function, BiPredicate, Long)

Definition of done

Implement fast thread switch for batch operations

Issue Links

• is related to: IGNITE-23616 Found a performance drop in Ignite benchmarks