[jira] [Updated] (IGNITE-21283) Improve client data streamer performance

["Evgeny Stanilovsky (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IGNITE-21283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Evgeny Stanilovsky updated IGNITE-21283:
----------------------------------------
    Fix Version/s: 3.2
                       (was: 3.1)

> Improve client data streamer performance
> ----------------------------------------
>
>                 Key: IGNITE-21283
>                 URL: https://issues.apache.org/jira/browse/IGNITE-21283
>             Project: Ignite
>          Issue Type: Improvement
>          Components: thin client
>    Affects Versions: 3.0.0-beta1
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.2
>
>
> * Embedded data streamer uses partition-based *org.apache.ignite.internal.table.InternalTable#upsertAll(java.util.Collection<org.apache.ignite.internal.schema.BinaryRowEx>, int)* method to upsert data, but client streamer uses *upsertAll* through public API
> * Embedded streamer performs batching per partition, client streamer batches per node (connection)
> Compare embedded and client streamer performance in different cases:
> * 1 node, 4 nodes
> * client connects to single node, client connects to all nodes
> Check if using per-partition approach with internal upsertAll API improves client streamer performance.
> *UPDATE*
> IGNITE-21402 changed the logic to use per-partition batches:
> * Compare client and embedded streamer performance
> * Check if per-node is better for client
> * Rename *perNodeParallelOperations* if necessary



--
This message was sent by Atlassian Jira
(v8.20.10#820010)