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 9E633200B95 for ; Tue, 13 Sep 2016 03:28:05 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 9CF3C160AC8; Tue, 13 Sep 2016 01:28:05 +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 E3CCA160AB8 for ; Tue, 13 Sep 2016 03:28:04 +0200 (CEST) Received: (qmail 3917 invoked by uid 500); 13 Sep 2016 01:28:04 -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 3907 invoked by uid 99); 13 Sep 2016 01:28:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Sep 2016 01:28:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id ACA00C0B4A for ; Tue, 13 Sep 2016 01:28:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.169 X-Spam-Level: * X-Spam-Status: No, score=1.169 tagged_above=-999 required=6.31 tests=[FREEMAIL_ENVFROM_END_DIGIT=0.25, RCVD_IN_DNSWL_NONE=-0.0001, SPF_FAIL=0.919] autolearn=disabled Received: from mx2-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id NyxB0I7FQWXg for ; Tue, 13 Sep 2016 01:27:59 +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 3AEEB60CE5 for ; Tue, 13 Sep 2016 01:27:59 +0000 (UTC) Received: from malf.nabble.com (unknown [162.253.133.59]) by mbob.nabble.com (Postfix) with ESMTP id 6E184310212B for ; Mon, 12 Sep 2016 18:25:41 -0700 (PDT) Date: Mon, 12 Sep 2016 18:27:57 -0700 (PDT) From: ght230 To: user@ignite.apache.org Message-ID: <1473730077400-7682.post@n6.nabble.com> Subject: Question about DisableExplicitGC MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Tue, 13 Sep 2016 01:28:05 -0000 I have read the aticle about jvm and system tuning (https://apacheignite.readme.io/docs/jvm-and-system-tuning#section-detailed-garbage-collection-stats). Below are sets of advanced JVM configurations for applications that might generate high numbers of temporary objects hence triggering long pauses due to garbage collection activities. -server -Xms8g -Xmx8g -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:+UseTLAB -XX:NewSize=128m -XX:MaxNewSize=128m -XX:MaxTenuringThreshold=0 -XX:SurvivorRatio=1024 -XX:+UseCMSInitiatingOccupancyOnly -XX:CMSInitiatingOccupancyFraction=40 -XX:MaxGCPauseMillis=1000 -XX:InitiatingHeapOccupancyPercent=50 -XX:+UseCompressedOops -XX:ParallelGCThreads=8 -XX:ConcGCThreads=8 -XX:+DisableExplicitGC I noticed it recommend to "DisableExplicitGC". I thought it is appropriate for the Ignite server. But if I run Ignite by client mode for Continuous query or Data Streamers, must this parameter "DisableExplicitGC" also be like that? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Question-about-DisableExplicitGC-tp7682.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.