[
https://issues.apache.org/jira/browse/IGNITE-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16342202#comment-16342202
]
ASF GitHub Bot commented on IGNITE-6699:
----------------------------------------
GitHub user 1vanan opened a pull request:
https://github.com/apache/ignite/pull/3442
IGNITE-6699 Optimize client-side data streamer performance
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/1vanan/ignite ignite-6699
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3442.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3442
----
commit f927404cbfe440f50d2b3970da930b6e11c93514
Author: Ivan <vanen31@...>
Date: 2017-11-30T12:08:14Z
benchmark on this case was developed
commit 7dcdfcf414a24aafd9a5a79349064f51dd7079d8
Author: Ivan <vanen31@...>
Date: 2017-12-26T16:35:58Z
streaming per batch was implemented.
commit 4fb853d944dda24692b3e67a905f6d0dc40f9cba
Author: Ivan <vanen31@...>
Date: 2018-01-15T15:38:32Z
some tests in DataStreamerAddDataKeyValueTest class were added
commit 5f509ed47aae4f3c579344e9b990fed7253f7c11
Author: 1vanan <vanen31@...>
Date: 2018-01-19T09:27:05Z
was added flushing in DataStreamerImpl.close() and per timeout
commit c17b74a436ffe7d80dc940b36a433f092f008d96
Author: Ivan <vanen31@...>
Date: 2018-01-24T14:12:36Z
code style changes
commit ae912906b6188bb0d70ba89b628bdffa685484cc
Author: Ivan <vanen31@...>
Date: 2018-01-27T13:27:21Z
synchronize buffer collections and also change timeout test
commit daab5027fb959c539b9084fa6ee06f32b4772d9f
Author: Ivan <vanen31@...>
Date: 2018-01-27T13:33:26Z
refactor addDataInternal: loadData method was added
----
> Optimize client-side data streamer performance
> ----------------------------------------------
>
> Key: IGNITE-6699
> URL: https://issues.apache.org/jira/browse/IGNITE-6699
> Project: Ignite
> Issue Type: Task
> Components: streaming
> Affects Versions: 2.3
> Reporter: Vladimir Ozerov
> Assignee: Ivan Fedotov
> Priority: Major
> Labels: iep-1, performance
> Fix For: 2.5
>
>
> Currently if a user has several server nodes and a single client node with
> single thread pushing data to streamer, he will not be able to load data at
> maximum speed. On the other hand, if he start several data loading threads,
> throughput will increase.
> One of root causes of this is bad data streamer design. Method
> {{IgniteDataStreamer.addData(K, V)}} returns new feature for every operation,
> this is too fine grained approach. Also it generates a lot of garbage and
> causes contention on streamer internals.
> Proposed implementation flow:
> 1) Compare performance of {{addData(K, V)}} vs {{addData(Collection)}}
> methods from one thread in distributed environment. The latter should show
> considerably higher throughput.
> 2) Users should receive per-batch features, rather than per-key.
> 3) Try caching thread data in some collection until it is large enough to
> avoid contention and unnecessary allocations.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
