Mailing-List: contact zookeeper-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: zookeeper-user@hadoop.apache.org
Received-SPF: pass (athena.apache.org: domain of ted.dunning@gmail.com
 designates 209.85.222.195 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        b=mDsTil1ESt/daQQw0UYMZqItKyK3sp71XlwcyTmUPavXnSKVfP+BWt1hM1LrDGXZC2
         z6htOPd3/Adet5Y/uNPwT+h4EVqFdYtA1i44QGCAhHVmnOFHOU0xkHkhIsjJnuoNE4jm
         ruq/HThunTFPTCHWyDTey2p51HWkyMuR5uQNA=
MIME-Version: 1.0
In-Reply-To: <4B9FC3EA.3010008@apache.org>
References: <828d4a961003152104h29bb6e34tfdbe62b99df89fc0@mail.gmail.com>
	<C7C504FB.316A2%mahadev@yahoo-inc.com>
 <828d4a961003161031h65100065qcf426f1eebdae08@mail.gmail.com>
	<4B9FC3EA.3010008@apache.org>
From: Ted Dunning <ted.dunning@gmail.com>
Date: Tue, 16 Mar 2010 10:59:37 -0700
Message-ID: <c7d45fc71003161059k556fc0aep12cad7bff4c4dced@mail.gmail.com>
Subject: Re: java heap size
To: zookeeper-user@hadoop.apache.org
Content-Type: multipart/alternative; boundary=000e0cd291a6bfd1e50481eeccd9

--000e0cd291a6bfd1e50481eeccd9
Content-Type: text/plain; charset=UTF-8

Of course, with only 32 - 200 MB of heap, almost anything will collect
pretty quickly!

If you are only storing a little bit of data (coordination, basically) then
a small heap might work fine.  Turn on gc logging and read what you get.  If
that is ok even with high load, then you should be fine.

One application where I saw a need for memory was when we stored user
sessions in ZK.

On Tue, Mar 16, 2010 at 10:46 AM, Patrick Hunt <phunt@apache.org> wrote:

> Add on top of that the poor performance of the GC in 1.6 jvms and more
> memory is critical/necessity.
>

--000e0cd291a6bfd1e50481eeccd9--