[IGNITE-19682] .NET: Thin 3.0: Combine tx.begin with first enlisted operation

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.0.0-beta1
• Fix Version/s: 3.0.0-beta2
• Component/s: thin client
• Labels: .NET ignite-3 performance
• Epic Link: AI3 Performance
• Assignee: Pavel Tupitsyn
• Reporter: Pavel Tupitsyn
• Created: 08/Jun/23 07:40
• Updated: 29/Jun/23 07:06

Description

Currently, client sends a separate TX_BEGIN request when the user invokes ITransactions.BeginAsync API:

• Extra network request.
• Chosen tx coordinator (server node that handles TX_BEGIN request) is random and in most cases won't be the primary node for enlisted keys.

Solution:

• On the client, do not send TX_BEGIN request when the user invokes ITransactions.BeginAsync. Instead, start the tx "on demand" when it is first used in some API.
• Send two requests at once to the same node where the first enlisted operation goes (according to partition awareness, if applicable).

Issue Links

• is a clone of: IGNITE-19681 Thin 3.0: Combine tx.begin with first enlisted operation