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 B3442200CD7 for ; Tue, 1 Aug 2017 23:03:34 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id B1DE5167F26; Tue, 1 Aug 2017 21:03:34 +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 0168C167F24 for ; Tue, 1 Aug 2017 23:03:33 +0200 (CEST) Received: (qmail 57977 invoked by uid 500); 1 Aug 2017 21:03:33 -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 57963 invoked by uid 99); 1 Aug 2017 21:03:32 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Aug 2017 21:03:32 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 6AF0A1A0139 for ; Tue, 1 Aug 2017 21:03:32 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.301 X-Spam-Level: X-Spam-Status: No, score=-0.301 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gridgain-com.20150623.gappssmtp.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id pW6VdHklv8h9 for ; Tue, 1 Aug 2017 21:03:31 +0000 (UTC) Received: from mail-ua0-f176.google.com (mail-ua0-f176.google.com [209.85.217.176]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 12EA35F572 for ; Tue, 1 Aug 2017 21:03:31 +0000 (UTC) Received: by mail-ua0-f176.google.com with SMTP id w45so12469732uac.5 for ; Tue, 01 Aug 2017 14:03:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gridgain-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=fonNBLan2hcGtW/7hFmy/oU7Ui0PXOgeq+y9TSCq04E=; b=cNVtAkcCXzHRji37G63X6mVBgSgDsiVGq+gAAaFUBPHc20FyQbZ43iUf2l3/z6tbcy 2FHFaBV/dPjDbDBJZ88inP1zJJlNBsgL5G6MdZFCkPzbHUy1GonySyj4zTfmeoMW+60d bc2il+0Ql9QuSfgdGlDZceg9+RWuv7wshffX6QgavZXg1iJ4n5AfEG+v0VQJfPr6xvz/ /8EmBHUY9wcjZV8Isrp7QHqznZ/hxfhJzVix9QXl9OHE0XhuQnPnOGjhjhIbLMsAxs1n XCb5NIzlH/R1ooZyMjBdglZWBv6Y7jJohQ8lxiCZGJ0s/92YYhsA1rLZAfV5LLM1VpLw 0y5Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=fonNBLan2hcGtW/7hFmy/oU7Ui0PXOgeq+y9TSCq04E=; b=sn9Nh+nQ7/8FHIO1VgrO1WGgFksB/b3oVWvgMGcqB/BQY9zawZ0xYum3Fc5Fauhvvz LsOJA28YuuMVo7DcWBRFo5qTr+Z/l0r3+cavzSEYBYP6mXFdCUmD2mdi6aUTh3iTo3jL GWZGTcznULFbwy7XCvb8IFSoVNjZEv1f8mn0XSJLZ8gr509O8OXyzg1zHApQ6OLldB/f EUZlZ8QzdZ6wu/ipivPRYhCr5+D5TkkNJrF2lTIE81ZcYlSWo1DFEL6ZEw15AqpkCAIW A2GzcWcW6K0oYP+g6h8DfLJv0YynLe3DUJnxeRtYft5idnDkTdrq1QlT46tjjXTOW/yk 7tOg== X-Gm-Message-State: AIVw1104aje9S983JS6CZsuv4LXgrH9PK6ynGmyR2X4HUZGPa9/U9GnI qW3ai2mgCGRmjF4uWwnUk19e1iO72yO2JAY= X-Received: by 10.176.88.66 with SMTP id p2mr15706574uac.181.1501621410325; Tue, 01 Aug 2017 14:03:30 -0700 (PDT) MIME-Version: 1.0 Received: by 10.176.2.150 with HTTP; Tue, 1 Aug 2017 14:03:29 -0700 (PDT) In-Reply-To: References: <39a952d7-613d-4eff-8ffc-1583c8c990d9@apache.org> From: Vladimir Ozerov Date: Wed, 2 Aug 2017 00:03:29 +0300 Message-ID: Subject: Re: [IGNITE-5717] improvements of MemoryPolicy default size To: dev@ignite.apache.org Content-Type: multipart/alternative; boundary="f403045f38f2c051130555b77a87" archived-at: Tue, 01 Aug 2017 21:03:34 -0000 --f403045f38f2c051130555b77a87 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Denis, No doubts you haven't heard about it - AI 2.1 with persistence, when 80% of RAM is allocated right away, was released several days ago. How do you think, how many users tried it already? Guys, Do you really think allocating 80% of available RAM is a normal thing? Take your laptop and check how many available RAM you have right now. Do you fit to remaining 20%? If not, then running AI with persistence with all defaults will bring your machine down. This is insane. We shold allocate no more than 1Gb, so that user can play with it without any problems. On Tue, Aug 1, 2017 at 10:26 PM, Denis Magda wrote: > My vote goes for option #1 too. I don=E2=80=99t think that 80% is too agg= ressive > to bring it down. > > IGNITE-5717 was created to fix the issue of the 80% RAM allocation on 64 > bit systems when Ignite works on top of 32 bit JVM. I=E2=80=99ve not hear= d of any > other complaints in regards the default allocation size. > > =E2=80=94 > Denis > > > On Aug 1, 2017, at 10:58 AM, dsetrakyan@apache.org wrote: > > > > I prefer option #1. > > > > =E2=81=A3D.=E2=80=8B > > > > On Aug 1, 2017, 11:20 AM, at 11:20 AM, Sergey Chugunov < > sergey.chugunov@gmail.com> wrote: > >> Folks, > >> > >> I would like to get back to the question about MemoryPolicy maxMemory > >> defaults. > >> > >> Although MemoryPolicy may be configured with initial and maxMemory > >> settings, when persistence is used MemoryPolicy always allocates > >> maxMemory > >> size for performance reasons. > >> > >> As default size of maxMemory is 80% of physical memory it causes OOME > >> exceptions of 32 bit platforms (either on OS or JVM level) and hurts > >> performance in setups when multiple Ignite nodes are started on the > >> same > >> physical server. > >> > >> I suggest to rethink these defaults and switch to other options: > >> > >> - Check whether platform is 32 or 64 bits and adapt defaults. In this > >> case we still need to address the issue with multiple nodes on one > >> machine > >> even on 64 bit systems. > >> > >> - Lower defaults for maxMemory and allocate, for instance, max(0.3 * > >> availableMemory, 1Gb). > >> This option allows us to solve all issues with starting on 32 bit > >> platforms and reduce instability with multiple nodes on the same > >> machine. > >> > >> > >> Thoughts and/or other options? > >> > >> Thanks, > >> Sergey. > > --f403045f38f2c051130555b77a87--