Hi, Amit.
I think the object size is OK for performance.
As for NPE, I think you should check if the entry exists in case you passed
the key which is not contained in cache:
if (mutableEntry.exists()) {
mutableEntry.setValue(...)
}
Check the javadoc for igniteCache.invoke about surrogate entries.
I don't see any "affinity code" in the provided sample.
Read here about affinity [1]
BTW, if you need to load many entries into cache and don't require
transactions, you should use DataStreamer API [2]
[1] https://apacheignite.readme.io/docs/affinity-collocation
[2] https://apacheignite.readme.io/docs/data-streamers
2016-06-07 12:56 GMT+03:00 pragmaticbigdata <[email protected]>:
> I tuned the application by batching the cache updates and making the query
> use the index. Wasn't able to make affinity calls work.
>
> Alexei, can you please provide your inputs on the affinity code?
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Simulating-Graph-Dependencies-With-Ignite-tp5282p5478.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
--
Best regards,
Alexei Scherbakov
