Hi, We are doing concurrent updates to Ignite. We have 2 nodes on the same machine. Our usecase is that we want to Order entry. It shoul dbe as fast as possible.
We saw the following hotspots when we analyzed with FlightRecorder:- Recheked the hot spots seem to be GridCacheMapEntry.obsolete which results in lots of contention and and GridShmemCommunicationClient.sendMessage which is called by the CommunicationSpi GridUnsafeMapSegment also has some extremely hot methods like advance etc, is there any way to reduce this ? Or is it necessary to allocate offheap memory etc? We have primary SYNC enabled, All our transactional caches are partitioned. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-performance-improvements-tp5623.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
