Hi Ignite Team,

I have stumbled across a problem when iterating over a persistence cache
that does not
fit into memory.

The partitioned cache consists of 50M entries across 3 nodes with a total
cache size of 3*80GB on the volumes.

I use either a ScanQuery or a SQL query over a non-indexed table. Both
results are the same.

It can take over an hour to iterate over the entire cache. The problem seems
to be that the cache is read in random 4kB (page size) chunks unparallelized
from the volume. A page size of 8kB exactly doubles the iteration speed.

Is this Ignite's default behaviour? Is there an option to enable a more
streaming like solution?
Of course, the order of the items in the cache doesn't matter.

Thanks,

Sebastian 



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Reply via email to