[jira] [Commented] (IGNITE-4624) ScanQuery shows poor performance.

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

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

GitHub user AMashenkov opened a pull request:

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

    IGNITE-4624: ScanQuery shows poor performance.

    

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

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

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

    https://github.com/apache/ignite/pull/1509.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 #1509
    
----
commit 12e231609d3a8e65540374ab3227b746c957e5d2
Author: Andrey V. Mashenkov <an...@gmail.com>
Date:   2017-01-30T15:29:42Z

    Fixed

----


> ScanQuery shows poor performance.
> ---------------------------------
>
>                 Key: IGNITE-4624
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4624
>             Project: Ignite
>          Issue Type: Improvement
>          Components: cache
>    Affects Versions: 1.8
>            Reporter: Andrew Mashenkov
>            Assignee: Andrew Mashenkov
>         Attachments: Change_keyIterator_to_entryIterator_for_local_scan_squery.patch, Demo.java
>
>
> I've found that ScanQuery use cache KeySet iterator which make cache peek\entry calls for getting value.
> It is look like we can avoid this calls by using EntrySet iterator for iterating over local partitions.
> Start point is GridCacheQueryManager.onheapIterator(). 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)