[ 
https://issues.apache.org/jira/browse/IGNITE-2874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206437#comment-15206437
 ] 

ASF GitHub Bot commented on IGNITE-2874:
----------------------------------------

GitHub user ptupitsyn opened a pull request:

    https://github.com/apache/ignite/pull/572

    IGNITE-2874 .NET: Fix DataStreamer performance

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ptupitsyn/ignite ignite-2874

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/572.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 #572
    
----
commit 82852ae6f86401b26d6dac1c0005c3c2252fb0b6
Author: Pavel Tupitsyn <[email protected]>
Date:   2016-03-22T13:50:23Z

    Fixing topSize

commit 37851b17b5df4e3aee8cf38a37a3aedd14e7122f
Author: Pavel Tupitsyn <[email protected]>
Date:   2016-03-22T13:55:31Z

    Fixing topSize

commit f167b1c08bbe5cadad0427e179f6a74d1dc392cb
Author: Pavel Tupitsyn <[email protected]>
Date:   2016-03-22T14:09:18Z

    topSize fixed

----


> .NET: Improve DataStreamer performance
> --------------------------------------
>
>                 Key: IGNITE-2874
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2874
>             Project: Ignite
>          Issue Type: Improvement
>          Components: platforms
>    Affects Versions: 1.6
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>            Priority: Critical
>             Fix For: 1.6
>
>
> DataStreamerExample takes ~50s to load 500K accounts, which is quite slow. 
> Quick profiling shows that DataStreamerBatch.Send spends a lot of time in 
> ReaderWriterLockSlim and GC. Only 13% is actual Java interop.
> Considerations:
> * Data streamer is mostly used from a single thread
> * Try to replace ReaderWriterLockSlim with simple lock, this can be faster
> * Try to reduce allocations



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to