ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-4624) ScanQuery shows poor performance.
Date Fri, 03 Mar 2017 14:32:45 GMT

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

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

Github user AMashenkov closed the pull request at:

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


> 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
>             Fix For: 2.0
>
>         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)

Mime
View raw message