ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Mashenkov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-4624) ScanQuery shows poor performance.
Date Fri, 27 Jan 2017 13:03:25 GMT

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

Andrew Mashenkov updated IGNITE-4624:
-------------------------------------
    Attachment: Demo.java

> 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
>         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.4#6332)

Mime
View raw message