Hello! Unfortunately I don't see any images.
future.get() just means that actual processing of request is happening in a different thread or on a different node. You should analyze thread dumps/flight recordings from all nodes in cluster to get complete picture. Regards, -- Ilya Kasnacheev чт, 26 дек. 2019 г. в 10:39, tarunk <[email protected]>: > Hi All, > > We had made few of our method call with cacheable annotation and using > Apache Ignite as cache manager. > Gris is of 12 node on-prem and cache config is as below. > > <bean id="rulesCacheConfiguration" > class="org.apache.ignite.configuration.CacheConfiguration" > p:name="rulesCache" > p:cacheMode="${cache.dynamicCacheMode:PARTITIONED}" > p:statisticsEnabled="${cache.rules.statisticsEnabled:true}" > p:nodeFilter-ref="nodeFilter" > p:nearConfiguration-ref="rulesCacheNearCacheConfiguration" > p:rebalanceBatchSize="${ignite.cache.rebalanceBatchSize:524288}" > > > p:rebalanceBatchesPrefetchCount="${ignite.cache.rebalanceBatchesPrefetchCount:2}" > p:rebalanceThrottle="${ignite.cache.rebalanceThrottle:0}" > p:rebalanceTimeout="${ignite.cache.rebalanceTimeout:10000}" > p:rebalanceMode="${ignite.cache.rebalanceMode:ASYNC}" > p:rebalanceDelay="${ignite.cache.rebalanceDelay:0}" > p:eagerTtl="${ignite.cache.eagerTtl:true}" > > > <property name="expiryPolicyFactory"> > <bean class="javax.cache.expiry.CreatedExpiryPolicy" > factory-method="factoryOf" > c:duration-ref="rulesDataExpiryDuration"/> > </property> > > <property name="groupName" value="StaticCache" /> > </bean> > > expiry-duration is 30 minutes. > We are experiencing the slowness in application and while tried to profile > the application and we noticed the the methods which are behind cacheable > annotation are taking time and SpringCache.get -> GridFutureAdapter.get() > taking most of the time, screenshot of profiling result is attached. > > Can anyone suggest what could be causing this ? > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
