ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ezhuravlev <e.zhuravlev...@gmail.com>
Subject Re: copyOnRead to false
Date Mon, 04 Sep 2017 18:37:11 GMT
Hi,

Could you describe your benchmarks? So we can understand whats could be
wrong here.

If the value is fetched from a remote node, you will always get a copy. If
you get the value locally, you can force Ignite to return the stored
instance by setting CacheConfiguration.setCopyOnRead(false) property, but
this should be used only in read-only scenario. It's not safe to modify this
instance because the serialized form will not be updated until you call
cache.put(), so the one that reads it will potentially get the old value.
Additionally, it can be concurrently serialized which can cause data
corruption. 

If you use BinaryMarshaller, with copyOnRead flag, Ignite stores serialized
copy in heap and do not copy object on each "get" (if the object does not
change after "get"):

Please share info about your benchmarks(or code) to investigation of this
problem.

Evgenii 



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Mime
View raw message