Data stored in an Ignite cache is always being serialized. There is no way to
avoid serialization routines.
If you’re not planning to use Ignite API over the local cache then I would
suggest using standard Java’s Map interface implementations.
—
Denis
> On Sep 9, 2016, at 4:51 PM, javastuff....@gmail.com wrote:
>
> Hello,
>
> It appears that entry is being serialized, eventhough cache is defined as
> LOCAL. Below is the configuration I used -
>
> <bean class="org.apache.ignite.configuration.CacheConfiguration">
> <property name="name" value="CATALOGDECLARATION"/>
> <property name="cacheMode" value="LOCAL"/>
> <property name="offHeapMaxMemory" value="#{100 * 1024L * 1024L}"/>
> <property name="memoryMode" value="OFFHEAP_TIERED"/>
> <property name="atomicityMode" value="TRANSACTIONAL"/>
> <property name="swapEnabled" value="false"/>
> <property name="backups" value="0" />
> </bean>
>
> 1. It will be performance overhead, when object is not shared and kept
> locally only.
> 2. It is losing state. To build a object we have to read from many slow
> subsystems providing read only data, example filesystem. and this
> information is transient for network flow, however object building is slow
> and hence need of caching instances in pool. this is a third party library
> engine which we are instantiating and hence can not move away from transient
> declarations.
>
> Is there a way to disable serialization for local cache?
>
> Similarly Near cache will be available locally after first read, but it is
> again in serialized form then it s performance over head as well.
>
> -Sam
>
>
>
>
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Local-cache-tp7645.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
