Github user AMashenkov closed the pull request at:
https://github.com/apache/ignite/pull/1509
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Alexey,
Would you please look at PR [1];
Can it be fixed the way implemented at PR or I've missed smth?
[1] https://issues.apache.org/jira/browse/IGNITE-4624
On Fri, Jan 27, 2017 at 7:57 PM, Dmitriy Setrakyan
wrote:
> On Fri, Jan 27, 2017 at 7:03 AM, Alexey Goncharuk <
> alexey.goncha...@gmail
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
On Fri, Jan 27, 2017 at 7:03 AM, Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:
> Andrey,
>
> From the top of my head I would guess that this is done so because
> keyIterator handles on-heap, off-heap and swap, while entrySet() return
> only on-heap entries. Please check that your change do
Andrey,
>From the top of my head I would guess that this is done so because
keyIterator handles on-heap, off-heap and swap, while entrySet() return
only on-heap entries. Please check that your change does not break
iteration with off-heap and swap enabled (if it does, it just means that we
need to
Hi Igniters,
I've found that ScanQuery iterates over partitions in non-optimal way. It
uses KeyIterator which gets value for each key via call to cache map.
I made a try to replace KeyIterator with EntryIterator to avoid cache map
lookups and got significant speed up, about 30%.
Is there some r
Andrew Mashenkov created IGNITE-4624:
Summary: ScanQuery shows poor performance.
Key: IGNITE-4624
URL: https://issues.apache.org/jira/browse/IGNITE-4624
Project: Ignite
Issue Type
