Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 74731 invoked from network); 10 Feb 2011 17:18:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 10 Feb 2011 17:18:44 -0000 Received: (qmail 92623 invoked by uid 500); 10 Feb 2011 17:18:41 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 92465 invoked by uid 500); 10 Feb 2011 17:18:38 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 92457 invoked by uid 99); 10 Feb 2011 17:18:38 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Feb 2011 17:18:38 +0000 X-ASF-Spam-Status: No, hits=4.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_BL_SPAMCOP_NET,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.161.172] (HELO mail-gx0-f172.google.com) (209.85.161.172) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Feb 2011 17:18:32 +0000 Received: by gxk27 with SMTP id 27so768395gxk.31 for ; Thu, 10 Feb 2011 09:18:10 -0800 (PST) MIME-Version: 1.0 Received: by 10.236.95.180 with SMTP id p40mr2121943yhf.73.1297358246442; Thu, 10 Feb 2011 09:17:26 -0800 (PST) Received: by 10.236.108.44 with HTTP; Thu, 10 Feb 2011 09:17:26 -0800 (PST) In-Reply-To: References: Date: Thu, 10 Feb 2011 12:17:26 -0500 Message-ID: Subject: Re: Out of control memory consumption From: Huy Le To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=002354867af06d5e4a049bf0c12e X-Virus-Checked: Checked by ClamAV on apache.org --002354867af06d5e4a049bf0c12e Content-Type: text/plain; charset=ISO-8859-1 Yes, we had setting at 75 but JVM did not have enough time to do GC, so it abort GC'ing. We lowered it to 50, but still had issue, so we lowered it again to 35. On Thu, Feb 10, 2011 at 12:11 PM, Oleg Anastasyev wrote: > Huy Le springpartners.com> writes: > > > Our CMS settings are: -XX:CMSInitiatingOccupancyFraction=35 > \ > -XX:+UseCMSInitiatingOccupancyOnly \ > > > > Occupancy Fraction = 35 seems very low value. You instructed GC to make > collection as soon as memory usage is at 35% - i.e. about 1G. This seems > very > low for production. > Did you tried another setting for this parameter ? 75 seems safe one. > > -- Huy Le Spring Partners, Inc. http://springpadit.com --002354867af06d5e4a049bf0c12e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Yes, we had setting at 75 but JVM did not have enough time to do GC, so it = abort GC'ing.=A0=A0 We lowered it to 50, but still had issue, so we low= ered it again to 35.

On Thu, Feb 10, 2011= at 12:11 PM, Oleg Anastasyev <oleganas@gmail.com> wrote:
Huy Le <huyle <at> springpartners.com> writes:

> Our CMS settings are:=A0=A0=A0=A0=A0=A0=A0 -XX:CMSInitiatingOccupancyF= raction=3D35 \=A0=A0=A0=A0=A0=A0=A0
-XX:+UseCMSInitiatingOccupancyOnly \=A0
>

Occupancy Fraction =3D 35 seems very low value. You instructed GC to = make
collection as soon as memory usage is at 35% - i.e. about 1G. This seems ve= ry
low for production.
Did you tried another setting for this parameter ? 75 seems safe one.




--
Huy Le
Spring Partn= ers, Inc.
http://springpadit.com =
--002354867af06d5e4a049bf0c12e--