X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id E73C9D7237 for ; Tue, 11 Oct 2005 15:11:07 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 79401-08 for ; Tue, 11 Oct 2005 18:11:01 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.196]) by svr1.postgresql.org (Postfix) with ESMTP id 932D8D6FCB for ; Tue, 11 Oct 2005 15:11:01 -0300 (ADT) Received: by wproxy.gmail.com with SMTP id 71so232799wra for ; Tue, 11 Oct 2005 11:11:02 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=rIGJAJBgGyCB726XCSdK9fJ3Z+4iKpYPj8kWI54LJlMcpexHuy5Ui5Dbkal4EIutPz36qAe1EzqyP/vn/QwXFv7u4An2UxUJx++KM3ni8LTTG5P92BthxSGzmbDlT0xVX0eR8jLDdhkDHYW31zMap6w6qGzrXucxH6YIdTsQ2ug= Received: by 10.54.69.10 with SMTP id r10mr3663000wra; Tue, 11 Oct 2005 11:11:02 -0700 (PDT) Received: by 10.54.84.8 with HTTP; Tue, 11 Oct 2005 11:11:02 -0700 (PDT) Message-ID: <33c6269f0510111111i676a2e50h57cd06757c59a3da@mail.gmail.com> Date: Tue, 11 Oct 2005 14:11:02 -0400 From: Alex Turner To: Alan Stange Subject: Re: Performance on SUSE w/ reiserfs Cc: pgsql-performance@postgresql.org In-Reply-To: <434BDA1E.5030804@rentec.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_185_19277859.1129054262473" References: <434ADD46.5060206@npcinternational.com> <6247.1128981289@sss.pgh.pa.us> <434AE7FF.4000705@npcinternational.com> <33c6269f0510110727q62a797a1g9493661e1dc905d4@mail.gmail.com> <434BD17E.7000605@rentec.com> <33c6269f0510110757v1632b9c5te578b699db922f45@mail.gmail.com> <434BDA1E.5030804@rentec.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.149 required=5 tests=[AWL=0.038, HTML_40_50=0.086, HTML_MESSAGE=0.001, RCVD_BY_IP=0.024] X-Spam-Level: X-Archive-Number: 200510/202 X-Sequence-Number: 14970 ------=_Part_185_19277859.1129054262473 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Well - to each his own I guess - we did extensive testing on 1.4, and it refused to allocate much past 1gig on both Linux x86/x86-64 and Windows. Alex On 10/11/05, Alan Stange wrote: > > Alex Turner wrote: > > > Perhaps this is true for 1.5 on x86-32 (I've only used it on x86-64) > > but I was more thinking 1.4 which many folks are still using. > > The 1.4.x JVM's will also work just fine with much more than 1GB of > memory. Perhaps you'd like to try again? > > -- Alan > > > > > On 10/11/05, *Alan Stange* > > wrote: > > > > Alex Turner wrote: > > > > > Realise also that unless you are running the 1.5 x86-64 build, java > > > will not use more than 1Gig, and if the app server requests more > > than > > > 1gig, Java will die (I've been there) with an out of memory error, > > > even though there is plenty of free mem available. This can > > easily be > > > cause by a lazy GC thread if the applicaiton is running high on > > CPU usage. > > > > On my side of Planet Earth, the standard non-x64 1.5 JVM will happily > > use more than 1G of memory (on linux and Solaris, can't speak for > > Windows). If you're running larger programs, it's probably a good > > idea > > to use the -server compiler in the JVM as well. I regularly run with > > -Xmx1800m and regularly have >1GB heap sizes. > > > > The standard GC will not cause on OOM error if space remains for the > > requested object. The GC thread blocks all other threads during its > > activity, whatever else is happening on the machine. The > > newer/experimental GC's did have some potential race conditions, but I > > believe those have been resolved in the 1.5 JVMs. > > > > Finally, note that the latest _05 release of the 1.5 JVM also now > > supports large page sizes on Linux and Windows: > > -XX:+UseLargePages this can be quite beneficial depending on the > > memory patterns in your programs. > > > > -- Alan > > > > > > ------=_Part_185_19277859.1129054262473 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Well - to each his own I guess - we did extensive testing on 1.4, and it refused to allocate much past 1gig on both Linux x86/x86-64 and Windows.

Alex

On 10/11/05, Alan Stange <stang= e@rentec.com> wrote:
Alex Turner wrote:

> Perhaps this is true for 1.5 on x86-32 (I've= only used it on x86-64)
> but I was more thinking 1.4 which many fol= ks are still using.

The 1.4.x JVM's will also work just fine with mu= ch more than 1GB of
memory.   Perhaps you'd like to try again?

-- Alan
=
>
> On 10/11/05, *Alan Stange* <stange@rentec.com
> <mailto: stange@rentec.com>> wrote:
>
>    = ; Alex Turner wrote:
>
>     > Realise a= lso that unless you are running the 1.5 x86-64 build, java
> &nb= sp;   > will not use more than 1Gig, and if the app server req= uests more
>     than
>     > = 1gig, Java will die (I've been there) with an out of memory error,
>&= nbsp;    > even though there is plenty of free mem availa= ble.  This can
>     easily be
>&= nbsp;    > cause by a lazy GC thread if the applicaiton i= s running high on
>     CPU usage.
>
>  &nbs= p;  On my side of Planet Earth, the standard non-x64 1.5 JVM will happ= ily
>     use more than 1G of memory (on linux an= d Solaris, can't speak for
>     Windows). &= nbsp;If you're running larger programs, it's probably a good
>     idea
>     to us= e the -server compiler in the JVM as well.  I regularly run with<= br>>     -Xmx1800m and regularly have >1GB heap s= izes.
>
>     The standard GC will not caus= e on OOM error if space remains for the
>     requested object.  The GC thread= blocks all other threads during its
>     activi= ty, whatever else is happening on the machine.   The
> = ;    newer/experimental GC's did have some potential race co= nditions, but I
>     believe those have been resolved in the 1.= 5 JVMs.
>
>     Finally, note that the late= st _05 release of the 1.5 JVM also now
>     supp= orts large page sizes on Linux and Windows:
>    = -XX:+UseLargePages   this can be quite beneficial depending on t= he
>     memory patterns in your programs.
><= br>>     -- Alan
>
>


------=_Part_185_19277859.1129054262473--