Hi, I tried capturing metrics for memory policies as well as from cache & nodes. Here is what I observed.
Before Updating Cache Node statistics - |Heap memory initialized | 1gb | | Heap memory used | 139mb | | Heap memory committed | 982mb | | Heap memory maximum | 982mb | | Non-heap memory initialized | 2mb | | Non-heap memory used | 47mb | | Non-heap memory committed | 48mb | | Non-heap memory maximum | 1gb | | Heap memory initialized | 1gb | | Heap memory used | 135mb | | Heap memory committed | 982mb | | Heap memory maximum | 982mb | | Non-heap memory initialized | 2mb | | Non-heap memory used | 45mb | | Non-heap memory committed | 46mb | | Non-heap memory maximum | 1gb | After updating cache- | Heap memory initialized | 1gb | | Heap memory used | 58mb | | Heap memory committed | 982mb | | Heap memory maximum | 982mb | | Non-heap memory initialized | 2mb | | Non-heap memory used | 55mb | | Non-heap memory committed | 56mb | | Non-heap memory maximum | 1gb | | Heap memory initialized | 1gb | | Heap memory used | 235mb | | Heap memory committed | 982mb | | Heap memory maximum | 982mb | | Non-heap memory initialized | 2mb | | Non-heap memory used | 53mb | | Non-heap memory committed | 54mb | | Non-heap memory maximum | 1gb | 1. non-heap memory used increased for both nodes. Does this confirm that data went to off-heap memory? 2. I am just doing a cacheStreamer.addData(). If data is going into off-heap memory, why is heap memory varying? 3. MemoryMetrics is actually not showing any results - >>> Memory Region Name: 40MB_Region_Eviction >>> Allocation Rate: 0.0 >>> Fill Factor: -1.0 >>> EvictionRate: 0.0 >>> TotalAllocatedPage: 0 >>> Memory Region Name: Default_Region >>> Allocation Rate: 0.0 >>> Fill Factor: -1.0 >>> EvictionRate: 0.0 >>> TotalAllocatedPage: 0 4. I captured CacheMetrics for the clustergroup as well. Even they are not showing any data - >>> Cache Metrics: CacheMetricsSnapshot [reads=0, puts=0, hits=0, misses=0, >>> txCommits=0, txRollbacks=0, evicts=0, removes=0, putAvgTimeNanos=0.0, >>> getAvgTimeNanos=0.0, rmvAvgTimeNanos=0.0, commitAvgTimeNanos=0.0, >>> rollbackAvgTimeNanos=0.0, cacheName=firstCache40MBP, offHeapGets=0, >>> offHeapPuts=0, offHeapRemoves=0, offHeapEvicts=0, offHeapHits=0, >>> offHeapMisses=0, offHeapEntriesCnt=0, offHeapPrimaryEntriesCnt=0, >>> offHeapBackupEntriesCnt=0, offHeapAllocatedSize=0, size=0, keySize=0, >>> isEmpty=true, dhtEvictQueueCurrSize=0, txThreadMapSize=0, >>> txXidMapSize=0, txCommitQueueSize=0, txPrepareQueueSize=0, >>> txStartVerCountsSize=0, txCommittedVersionsSize=0, >>> txRolledbackVersionsSize=0, txDhtThreadMapSize=0, txDhtXidMapSize=0, >>> txDhtCommitQueueSize=0, txDhtPrepareQueueSize=0, >>> txDhtStartVerCountsSize=0, txDhtCommittedVersionsSize=0, >>> txDhtRolledbackVersionsSize=0, isWriteBehindEnabled=false, >>> writeBehindFlushSize=-1, writeBehindFlushThreadCnt=-1, >>> writeBehindFlushFreq=-1, writeBehindStoreBatchSize=-1, >>> writeBehindTotalCriticalOverflowCnt=0, writeBehindCriticalOverflowCnt=0, >>> writeBehindErrorRetryCnt=0, writeBehindBufSize=-1, >>> keyType=java.lang.Object, valType=java.lang.Object, isStoreByVal=true, >>> isStatisticsEnabled=false, isManagementEnabled=false, >>> isReadThrough=false, isWriteThrough=false] -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite2-0-and-Memory-Policies-tp12550p12577.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
