Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-21283

Improve client data streamer performance

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 3.0.0-beta1
    • 3.1
    • thin client

    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.

      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

      Attachments

        Issue Links

          Activity

            People

              ptupitsyn Pavel Tupitsyn
              ptupitsyn Pavel Tupitsyn
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: