Java – performance degradation upgrade from hazelcast 2.5 to 3

Due to known (fixed) errors in hazelcast 2.5, we have determined that this will be the next upgrade candidate for our project But after putting in the latest version (3.2.2), we performed very badly

How we use hazelcast:

>Two nodes > multiple IMAP instances (about 7 maps in total) > both nodes update the map > there is a lot of content on the map > enable near cache to speed up reading

When using hazelcast 2.5, we provide good performance instead of using map Values (), we provide all the contained key maps Getall (containedkeys) list We track containskeys by adding entrylistener to the map, which stores containskeys in the concurrency set This is added by a colleague. It feels like a hacker, but work is like a charm

Now, when we upgrade to hazelcast 3.2 2, we will immediately see Java IO, for example, see the following code snippet for appdynamics:

com.hazelcast.map.proxy.MapProxyImpl:getAll:326 (method time = 0 ms,total time = 18938 ms)
 com.hazelcast.map.proxy.MapProxySupport:getAllObjectInternal:495 (method time = 0 ms,total time = 18938 ms)
  com.hazelcast.map.MapService:toObject:852 (method time = 0 ms,total time = 18938 ms)
   com.hazelcast.spi.impl.NodeEngineImpl:toObject:156 (method time = 0 ms,total time = 18938 ms)
    com.hazelcast.nio.serialization.SerializationServiceImpl:toObject:221 (method time = 0 ms,total time = 18938 ms)
     com.hazelcast.nio.serialization.StreamSerializerAdapter:read:59 (method time = 0 ms,total time = 18938 ms)
      com.hazelcast.nio.serialization.DefaultSerializers$ObjectSerializer:read:185 (method time = 0 ms,total time = 18938 ms)
       java.io.ObjectInputStream:readObject:370 (method time = 3398 ms,total time = 18938 ms)
        java.io.ObjectInputStream:readObject:370 (method time = 15540 ms,total time = 15540 ms)

This is not what we saw in hazelcast 2.5, but in 3.2 There are two It brought our application to a complete standstill There is nothing wrong with replacing jar with 2.5 again (and renaming entry to mapentry)

What could have caused this? Maybe it doesn't use near cache anymore?

Solution

Have you seen this Google group ticket problem?

https://groups.google.com/forum/# ! topic/hazelcast/ivk6hzk2YwA

The reason for the problem is explained here

https://github.com/hazelcast/hazelcast/issues/553