Return-Path: Delivered-To: apmail-incubator-harmony-dev-archive@www.apache.org Received: (qmail 51108 invoked from network); 14 Sep 2006 23:52:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 14 Sep 2006 23:52:33 -0000 Received: (qmail 76320 invoked by uid 500); 14 Sep 2006 23:52:26 -0000 Delivered-To: apmail-incubator-harmony-dev-archive@incubator.apache.org Received: (qmail 76269 invoked by uid 500); 14 Sep 2006 23:52:26 -0000 Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: harmony-dev@incubator.apache.org Delivered-To: mailing list harmony-dev@incubator.apache.org Received: (qmail 76258 invoked by uid 99); 14 Sep 2006 23:52:26 -0000 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of xiaofeng.li@gmail.com designates 66.249.92.171 as permitted sender) Received: from [66.249.92.171] (HELO ug-out-1314.google.com) (66.249.92.171) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Sep 2006 16:52:26 -0700 Received: by ug-out-1314.google.com with SMTP id y2so233618uge for ; Thu, 14 Sep 2006 16:51:04 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=VTtj9a1Re15WpoZroxBztHVIeUJA64+8XlH9ySO9AwkZyhtcxN8rp27SKTlCIaAs5MLXFD8CCOWquG0xniyv83wJWnOZU8hXqNQglmVkDLk7zRA8Aw2slHQJ/50H78Wizc6ZBj7VAL8d1ZCpAjveeRl9ibmlVGt+b/LGOwrlEfU= Received: by 10.66.216.6 with SMTP id o6mr5138143ugg; Thu, 14 Sep 2006 16:51:04 -0700 (PDT) Received: by 10.67.10.9 with HTTP; Thu, 14 Sep 2006 16:51:04 -0700 (PDT) Message-ID: <9623c9a50609141651j4c82e2d8pf845ccfdf4550533@mail.gmail.com> Date: Fri, 15 Sep 2006 07:51:04 +0800 From: "Xiao-Feng Li" To: harmony-dev@incubator.apache.org Subject: Re: [General VM] GC strategy:how to garbage collect short-lived objects quickly. In-Reply-To: <12385bbd0609141213v42762762gcac8d3ff48434be7@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <9623c9a50609132353k49ed4fei18b634bf1e074212@mail.gmail.com> <12385bbd0609141213v42762762gcac8d3ff48434be7@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On 9/15/06, Ivan Volosyuk wrote: > Well, common practise is to allocate most of the physical memory for > java heap and let the GC to deal with it. Different GC algorithms will > produce different pause times with different frequencies. > > For your case, I think, it will be optimal to have old generation of > objects living untouched most of the GCs. The rest of the heap is for > young generation objects. GC can be made to occur more frequently if > we collect only part of the young generation space: the oldest chunk > of young generation at a time. There is a trade-off between portion of > heap collected and GC frequency, of cause. > > Other techniques like the JIT's thread-local allocation can also help. > -- > Ivan Yes, agreed. the trade-off in GC frequency should be well understood in order to achieve best performance. Thanks, xiaofeng --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org For additional commands, e-mail: harmony-dev-help@incubator.apache.org