> Curious to know How fast is Disk KV persistence ? since Ignite iterates over all keys and indexes to do the computation. Is Disk KV persistence is as efficient as in other stable NoSQL database like Cassandra ? > Does the number of partitions helps in better key lookup access from Disk > ? > If such performance level is not possible can we attach different KV > solution like Xodus, BerkeyDB Java editon etc.
Ignite's persistence is fully production-grade. Given proper configuration and integration, you should be able to get the necessary performance. The cluster specs you've provided seem fine, although it's hard to tell what are the exact requirements for your case. > Can I opt for certain tables to be Disk only and never get cached on heap > regardless of access pattern ? No. Ignite's in-memory data and disk are deeply integrated, when an entry is read from the disk it will be loaded in to the memory first. What is the use case for this? Why do you want certain tables not to have an in-memory cache? > Can I embed custom data encryption scheme for Disk persistence ? No, Ignite currently doesn't support encryption of the data on disk. Thanks, Stan -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
