Hi Sudhir, There are 3 things to consider:
1) Capacity planning - how much memory do you need for your data? Depending on type, 30-50 properties can take very different amount of memory to store. - n+4+1 for strings, where n is size in utf8 encoding - 4+1 bytes for int - 8+1 bytes for long and so on (every field takes extra byte for type code) More details: https://apacheignite.readme.io/docs/capacity-planning 2) JVM settings Ignite does not store your data in Java Heap, but some memory is still required for processing See https://apacheignite.readme.io/docs/jvm-and-system-tuning#section-garbage-collection-tuning 3) Ignite DataRegionConfiguration Ignite stores cache data in so-called Data Regions, in unmanaged heap (aka "offheap"). By default, only one region is configured with max size set to 20% of available RAM. You may want to increase this by changing IgniteConfiguration.DataStorageConfiguration.DefaultDataRegionConfiguration More details: https://apacheignite.readme.io/docs/durable-memory-tuning On Wed, Nov 13, 2019 at 4:13 AM Sudhir Patil <[email protected]> wrote: > Hi All, > > What should be configuration changes required for storing large data e.g. > 10 million records of custom class objects having around 30- 50 properties? > > I am using basic default configuration for Ignite.net. > JvmOptions used are like > -Djava.net.preferIPv4Stack=true > -Xms512m > -XX:+UseG1GC > -XX:+DisabkeExplicitGC > > Regards, > Sudhir > > > > -- > Thanks & Regards, > Sudhir Patil, > +91 9881095647. >
