Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id EF9E2200B6B for ; Thu, 21 Jul 2016 05:32:25 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id EE4CC160A64; Thu, 21 Jul 2016 03:32:25 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 4147E160A89 for ; Thu, 21 Jul 2016 05:32:25 +0200 (CEST) Received: (qmail 1527 invoked by uid 500); 21 Jul 2016 03:32:24 -0000 Mailing-List: contact user-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ignite.apache.org Delivered-To: mailing list user@ignite.apache.org Received: (qmail 1517 invoked by uid 99); 21 Jul 2016 03:32:24 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Jul 2016 03:32:24 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 9C40CC8229 for ; Thu, 21 Jul 2016 03:32:23 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.652 X-Spam-Level: X-Spam-Status: No, score=0.652 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_NONE=-0.0001, SPF_NEUTRAL=0.652] autolearn=disabled Received: from mx2-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id ltdL8j26wwm0 for ; Thu, 21 Jul 2016 03:32:21 +0000 (UTC) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx2-lw-eu.apache.org (ASF Mail Server at mx2-lw-eu.apache.org) with ESMTP id 283745FE66 for ; Thu, 21 Jul 2016 03:32:21 +0000 (UTC) Received: from malf.nabble.com (unknown [162.253.133.59]) by mbob.nabble.com (Postfix) with ESMTP id C860B2CF225B for ; Wed, 20 Jul 2016 20:08:51 -0700 (PDT) Date: Wed, 20 Jul 2016 20:15:10 -0700 (PDT) From: kwon To: user@ignite.apache.org Message-ID: <1469070910585-6435.post@n6.nabble.com> Subject: Question about Tier Propagation of Memory MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Thu, 21 Jul 2016 03:32:26 -0000 Hi, I have a some question about Tier Propagation of Memory, i.e, cached data moving from on-heap to off-heap memory and viceversa. I read below, and wonder.. ======================= As data gets colder (not accessed) Ignite will optionally migrate it from On-Heap memory to Off-Heap memory, and from Off-Heap memory to Swap (disk) storage. Whenever some data is accessed, it will immediately be propagated to the top tier pushing some other colder data down the next memory tier. from https://ignite.apache.org/features/datagrid.html ======================= if I use "OFFHEAP_TIERED" as memory mode instead of "ONHEAP_TIERED", then does it also occur data propagation from down tier(i.e, off-heap) to top tier(i.e, on-heap)? for example, I access data like as get(some_key), then does the data(value mapping by key) moved from off-heap to on-heap? Or in "OFFHEAP_TIERED" mode, the data is always exist on off-heap, and can access data without moving to on-heap? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Question-about-Tier-Propagation-of-Memory-tp6435.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.