You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Andrew Mashenkov (JIRA)" <ji...@apache.org> on 2017/02/08 19:22:41 UTC

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

     [ https://issues.apache.org/jira/browse/IGNITE-4624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Mashenkov reassigned IGNITE-4624:
----------------------------------------

    Assignee: Andrew Mashenkov

> 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)