Hi!
The overhead for an entry in Ignite is much bigger than an SQL server
record, you have something like 200 byte overhead for each entry and the
binary format used in an SQL server is more compact compared to the
binary storage format used in Ignite, so if your records are small the
size you have might be correct.
Are you keeping all of the data in ram at the same time ? wouldn't it be
better to keep it in the SQL server and cache a smaller set of records
in Ignite ?
Are you copying the data into Ignite as a one time process or are you
using a CacheStoreAdapter ?
The section about durable memory / eviction policy in the documentation
explains how to control the amount of ram that is used.
Mikael
Den 2018-06-26 kl. 10:11, skrev Michaelikus:
Hi dear dr. Allcome ;)
I have an table in MSSQL which size is 4GB
I've transfer it to cache and it's size takes more tan 80GB(5 nodes per 22GB
offheap each)
Can you advise me how i can control size of caches for monitoring?
Regards,
Michael.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
