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 0AE2B200C61 for ; Tue, 25 Apr 2017 13:31:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 0954E160BB6; Tue, 25 Apr 2017 11:31:09 +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 4ECA0160BB3 for ; Tue, 25 Apr 2017 13:31:08 +0200 (CEST) Received: (qmail 20801 invoked by uid 500); 25 Apr 2017 11:31:07 -0000 Mailing-List: contact issues-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 issues@ignite.apache.org Received: (qmail 20791 invoked by uid 99); 25 Apr 2017 11:31:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Apr 2017 11:31:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 27620188332 for ; Tue, 25 Apr 2017 11:31:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id iOv6hDYyQtOq for ; Tue, 25 Apr 2017 11:31:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 0B02A5FCA1 for ; Tue, 25 Apr 2017 11:31:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 7A508E0942 for ; Tue, 25 Apr 2017 11:31:04 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 3184521B55 for ; Tue, 25 Apr 2017 11:31:04 +0000 (UTC) Date: Tue, 25 Apr 2017 11:31:04 +0000 (UTC) From: "Alexey Goncharuk (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (IGNITE-5024) Default MemoryPolicy settings improvements MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 25 Apr 2017 11:31:09 -0000 [ https://issues.apache.org/jira/browse/IGNITE-5024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15976477#comment-15976477 ] Alexey Goncharuk edited comment on IGNITE-5024 at 4/25/17 11:30 AM: -------------------------------------------------------------------- [~dsetrakyan], sure, examples are below. I'll use this proposed setting in them and at the end explain how configuration looks like without it. I would consider Memory Policy configuration on three different levels. *Fully default*: user doesn't need to specify anything, default MemoryPolicy with default name and 80% of available RAM size is created. *Semi-default*: user wants to override this "80% RAM" setting. All is needed is to use the following configuration: {code:xml} {code} *Fully customized*: user defines everything by his/her own including name and size of default Memory Policy. {code:xml} {code} Proposed setting allows to simplify semi-default level; without it user needs to use verbose fully-customized syntax in order to adjust only default Memory Policy size. was (Author: sergey-chugunov): [~dsetrakyan], sure, examples are below. I'll use this proposed setting in them and at the end explain how configuration looks like without it. I would consider Memory Policy configuration on three different levels. *Fully default*: user doesn't need to specify anything, default MemoryPolicy with default name and 80% of available RAM size is created. *Semi-default*: user wants to override this "80% RAM" setting. All is needed is to use the following configuration: {code:xml} {code} *Fully customized*: user defines everything by his/her own including name and size of default Memory Policy. {code:xml} {code} Proposed setting allows to simplify semi-default level; without it user needs to use verbose fully-customized syntax in order to adjust only default Memory Policy size. > Default MemoryPolicy settings improvements > ------------------------------------------ > > Key: IGNITE-5024 > URL: https://issues.apache.org/jira/browse/IGNITE-5024 > Project: Ignite > Issue Type: Improvement > Components: cache > Reporter: Sergey Chugunov > Assignee: Alexey Goncharuk > Labels: general > Fix For: 2.0 > > > h2. Notes > Currently when user doesn't specify any MemoryPolicy configuration a default one is created. It has a fixed size of 1 GB which seems to be too rigid. > Also when user wants to override size of the default MemoryPolicy, the full syntax of this configuration must be used; it is cumbersome in such simple case. > h2. Acceptance Criteria > # Default MemoryPolicy is created with size of 80% of physical memory available on machine. > # New configuration property *defaultMemoryPolicySize* is introduced in *memoryConfiguration* section to allow user to specify exact size in bytes without applying verbose syntax of *memoryPolicyConfiguration* section. -- This message was sent by Atlassian JIRA (v6.3.15#6346)