Hi, Because Ignite always serialize data, we are not able to take advantage of Near cache where cached object are heavy interms of serialization/de-serilalization and no requirement of query or eviction. We are taking about 5 min vs 2 hours difference, if we do not cache meta information of frequently accessed small number of objects.
I am working on Java's standard map based implementation to simulate Near cache where local heap has non-serialized object backed by partitioned ignited distributed cache. Cache invalidation is a challenge where one node invalidates partitioned distributed cache and now we have to invalidate local copy of same cache form each each node. Need experts opinion on my POC - For a particular cache add EVT_CACHE_OBJECT_REMOVED cache event listener. Now remove cache event will be generated on local node and remote node who own that cache key. Remove event handler/actor publish a message to a topic. On receiving message on topic each node will remove object from local map based copy. Question - 1. Do you see any issue with this kind of implementation when cache invalidation will be very less, but read will be more frequent? 2. Approximately how much delay one should expect during event generation and publishing messages to all nodes? 3. I have observed remove Event is generated only on acting local node or owner node. So need to combine Event with Topic. Is there any other way this can be achieved? 4. In terms of performance should we use - - Should we use local listener or remote listener? In POC I have added remote listener. - Should we use sendOrderd or send? 4. Is there any specific sizing need to be done for REMOVE event and TOPIC? We have around 20 such cache and I am planning to have a single topic. Regarding topology - At minimum 2 nodes with 20 GB off-heap. Thanks, -Sam -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Near-cache-tp8192.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
