ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexey Goncharuk <alexey.goncha...@gmail.com>
Subject Re: ScanQuery shows poor performance.
Date Fri, 27 Jan 2017 15:03:21 GMT

>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 implement a correct entry iterator for off-heap as well).


2017-01-27 16:06 GMT+03:00 Andrey Mashenkov <andrey.mashenkov@gmail.com>:

> 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 reason to use KeyIterator for this or some other use cases?
> I've created a ticket [1] with patch and test attached.
> [1] https://issues.apache.org/jira/browse/IGNITE-4624
> Regards.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message