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 D5361200C6B for ; Tue, 18 Apr 2017 03:00:20 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id CF36A160BAE; Tue, 18 Apr 2017 01:00:20 +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 2005A160BAB for ; Tue, 18 Apr 2017 03:00:19 +0200 (CEST) Received: (qmail 97740 invoked by uid 500); 18 Apr 2017 01:00:19 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 97728 invoked by uid 99); 18 Apr 2017 01:00:19 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Apr 2017 01:00:19 +0000 Received: from [192.168.75.221] (c-73-222-138-29.hsd1.ca.comcast.net [73.222.138.29]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 0B52A1A00A6 for ; Tue, 18 Apr 2017 01:00:18 +0000 (UTC) From: Denis Magda Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Page Memory behavior with default memory policy Date: Mon, 17 Apr 2017 18:00:17 -0700 References: <51CE27F0-3225-4085-8D48-6395E56E069F@apache.org> To: dev@ignite.apache.org In-Reply-To: Message-Id: <08A3FB3A-833D-4ABB-A813-66E43927D659@apache.org> X-Mailer: Apple Mail (2.3273) archived-at: Tue, 18 Apr 2017 01:00:21 -0000 Dmitriy, All the nodes will request its own continuous memory region that takes = 70-80% of all RAM from an underlying operation system. However, the = operating system will not outfit the nodes with physical pages mapped to = RAM immediately allowing every node's process to start successfully. The = nodes will communicate to RAM via a virtual memory which in its turn = will give an access to physical pages whenever is needed applying low = level eviction and swapping techniques. Alex G., please confirm that we=E2=80=99re applying on this low level = guarantees in our page memory impl. =E2=80=94 Denis > On Apr 17, 2017, at 5:50 PM, Dmitriy Setrakyan = wrote: >=20 > On Mon, Apr 17, 2017 at 5:46 PM, Denis Magda = wrote: >=20 >> Guys, >>=20 >> If a memory region is not expandable can we calculate the size of the >> default one automatically rather than setting it to predefined value = like 1 >> GB, 512 MB, etc. ? >>=20 >> For instance, when a node is being started it finds out how much RAM = is >> available and requests 70-80% of it for the default memory region = usage. >> This should help us avoid this usability issue caused by the fact = that we >> hard code the size. >>=20 >=20 > Denis, what happens if user plans to start multiple nodes on the same = box?