Hello! First of all, Ignite is a data grid designed for gigabytes of data. So 71M is not significant.
Secondly, your cache probably has 1024 partitions configured by default, and each of those has quite some metadata and directory structure. Try decreasing that number if you plan on having very few data in cache. Regards, -- Ilya Kasnacheev пт, 22 февр. 2019 г. в 15:39, newigniter <[email protected]>: > created a table and inserted 9013 records in it. > The table has 17 columns and the total size of the data before import into > ignite is 282,625 bytes. > I have native persistence enabled and have 2 nodes in my cluster. Data is > replicated to both nodes. > I am using ignite 2.7. > After import into ignite I check how much disk space it took in order to > save this data into ignite. > I find this table cache in my work folder inside db. When I check the size > of this cache it is: *71Mb*. > What I do is check the cache sizes with the following command: *du -h * > > Presumably, I can check the cache sizes on this way, I don't understand why > ignites takes 71Mb for something that outside ignite has the size of > 282,625 > bytes. I read in the documentation that data in ignite will be 2.5 - 3 > times > bigger and that each index adds 30% in size. I have 2 indexes created and > with all of this, I still don't understand why ignite takes 71Mb for this? > > > 1.) Can I check sizes in ignite on the way that I do? If no, how can I do > it? > 2.) Why Ignite takes so much disk space for so little data? > 3.) If in this case, ignite stores this data on disk and takes 71Mb, will > it > require the same amount of RAM presumably that all of this data is loaded > into memory? > > This is not an isolated case. I have few other tables and comparing sizes > in > ignite with sizes of data outside ignite and I have the same issue. > > Thank you. > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
