Return-Path: 
 <user-return-3372-apmail-ignite-user-archive=ignite.apache.org@ignite.apache.org>
X-Original-To: apmail-ignite-user-archive@minotaur.apache.org
Delivered-To: apmail-ignite-user-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id D195B19B74
	for <apmail-ignite-user-archive@minotaur.apache.org>;
 Mon, 28 Mar 2016 20:18:09 +0000 (UTC)
Received: (qmail 80680 invoked by uid 500); 28 Mar 2016 20:18:09 -0000
Delivered-To: apmail-ignite-user-archive@ignite.apache.org
Received: (qmail 80637 invoked by uid 500); 28 Mar 2016 20:18:09 -0000
Mailing-List: contact user-help@ignite.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@ignite.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@ignite.apache.org>
List-Post: <mailto:user@ignite.apache.org>
List-Id: <user.ignite.apache.org>
Reply-To: user@ignite.apache.org
Delivered-To: mailing list user@ignite.apache.org
Received: (qmail 80623 invoked by uid 99); 28 Mar 2016 20:18:09 -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; Mon, 28 Mar 2016 20:18:09 +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 2C879180479
	for <user@ignite.apache.org>; Mon, 28 Mar 2016 20:18:09 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd3-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 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 MiO7GwBqUswB for <user@ignite.apache.org>;
	Mon, 28 Mar 2016 20:18:07 +0000 (UTC)
Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15])
	by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP
 id 2866E5FAE1
	for <user@ignite.apache.org>; Mon, 28 Mar 2016 20:18:06 +0000 (UTC)
Received: from malf.nabble.com (unknown [162.253.133.59])
	by mbob.nabble.com (Postfix) with ESMTP id A740823EEA89
	for <user@ignite.apache.org>; Mon, 28 Mar 2016 13:07:03 -0700 (PDT)
Date: Mon, 28 Mar 2016 13:04:49 -0700 (PDT)
From: abarbaro <abarbaro@powercosts.com>
To: user@ignite.apache.org
Message-ID: <1459195489581-3719.post@n6.nabble.com>
In-Reply-To: <1458931784681-3682.post@n6.nabble.com>
References: <1458931784681-3682.post@n6.nabble.com>
Subject: Re: Ignite Cache - High Memory Overhead caused by
 GridCircularBuffer$Item instances
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Ok, I have done more research and I think I understand the effect of these
two parameters.  I think my original question is resolved.


Also, I have found that this parameter has a huge performance impact as
well:

<bean class="org.apache.ignite.configuration.CacheConfiguration">
		...
		<property name="eagerTtl" value="false"/> 
		...
</bean>

When eagerTtl is true (default), Ignite will start a thread per cache to try
to delete entries as quick as possible.  I was running tests with 1,000
caches and the number of threads was overwhelming the nodes.

Thanks for all your help!



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Cache-High-Memory-Overhead-caused-by-GridCircularBuffer-Item-instances-tp3682p3719.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.