Hi Andres, Scan query with partition number was created exactly to iterate over partitions. Please share your numbers for scan query and local iteration. For now I do not see any obvious reason why it could be much slower than iteration.
Vladimir. On Wed, Mar 30, 2016 at 2:03 AM, abarbaro <[email protected]> wrote: > A couple of things to clarify the request/question about an API to iterate > over cache entries on given partitions: > a) I'm only talking about iterating locally (i.e. it will only iterate > on > the localEntries). > b) In terms of semantics, I was thinking about overload for the existing > localEntries method > for (Entry<K, V> entry : > Ignition.localIgnite().cache(cacheName).localEntries(partitions, > CachePeekMode.PRIMARY)) > > where partitions is an int[] that contains the partitions to iterate > over. > > > I'm not suggesting an implementation, but simply trying to clarify my > previous comment. > > Andres > > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Ignite-Cache-and-Compute-Performance-tp3722p3752.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
