[
https://issues.apache.org/jira/browse/IGNITE-21283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-21283:
------------------------------------
Description:
* 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.
> 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.0.0-beta2
>
>
> * 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
