ali wrote > It seems that ignite uses arraylist to collect itterated data. (no > pagination is done to collect data). ??
I believe that you are scanning the cache within the process of the node that caches the data. For this approach, I would recommend simple iteration over cache (Cache interface implements Iterable) and analyzing values. If you start another client node, and use Scan query from that node, then the data will be paginated and returned back page-by-page. For this, just start up another node in client mode (Ignitition.setClientMode(true) method) and issue the same scan query. ali wrote > I' would be also interested in performance stats if available and > recomended configurations. Please take a look at Yardstick framework, specifically Ignite benchmarks: https://github.com/yardstick-benchmarks/yardstick-ignite I have also written a few blogs on benchmarking Ignite: http://gridgain.blogspot.com/2015/04/benchmarking-data-grids-apache-ignite.html http://gridgain.blogspot.com/2015/05/benchmarking-data-grids-apache-ignite.html -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Data-Cache-memory-crash-tp341p354.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
