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

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

GitHub user gvvinblade opened a pull request:

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

    IGNITE-5658

    

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

    $ git pull https://github.com/gridgain/apache-ignite ignite-5658

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

    https://github.com/apache/ignite/pull/2397.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 #2397
    
----
commit 8909ef69ab03c37b1bf99e25335b6f385f1ebbc3
Author: Igor Seliverstov <gvvinbl...@gmail.com>
Date:   2017-08-04T12:45:01Z

    IGNITE-5918 Adding and searching objects in index tree produces a lot of 
garbage

commit e6f7b3053fc29a0a6bdfd364b71709a72f920a12
Author: Igor Seliverstov <gvvinbl...@gmail.com>
Date:   2017-08-04T12:47:39Z

    IGNITE-5658 Optimizations for data streamer
    IGNITE-5921 Reduce contention for free list access

----


> Optimizations for data streamer
> -------------------------------
>
>                 Key: IGNITE-5658
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5658
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Yakov Zhdanov
>            Assignee: Yakov Zhdanov
>              Labels: performance
>             Fix For: 2.2
>
>         Attachments: benchmark-full.properties
>
>
> Data streamer can be improved with this:
> -batch on per-partition basis and send batches to striped pool (for 
> allowOverwirte=false)
> -New default - perNodeParallelOps should be twice CPU count of a remote node 
> (if not set by user, if set then parallelOps for every node is the value 
> provided by user)
> -wait stable topology error should be output as warn



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to