X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 30CF1D1B557 for ; Wed, 22 Oct 2003 21:37:30 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 99232-04 for ; Wed, 22 Oct 2003 18:37:01 -0300 (ADT) Received: from lakemtao02.cox.net (lakemtao02.cox.net [68.1.17.243]) by svr1.postgresql.org (Postfix) with ESMTP id 7D3C5D1B515 for ; Wed, 22 Oct 2003 18:36:55 -0300 (ADT) Received: from lhosts ([68.11.66.83]) by lakemtao02.cox.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP id <20031022213654.GTYN17750.lakemtao02.cox.net@lhosts> for ; Wed, 22 Oct 2003 17:36:54 -0400 Subject: Re: Tuning for mid-size server From: Ron Johnson To: PgSQL Performance ML In-Reply-To: References: <200310211012.15845.josh@agliodbs.com> Content-Type: text/plain Message-Id: <1066858611.12532.223.camel@haggis> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Wed, 22 Oct 2003 16:36:51 -0500 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/588 X-Sequence-Number: 4336 On Tue, 2003-10-21 at 14:27, Christopher Browne wrote: > In the last exciting episode, josh@agliodbs.com (Josh Berkus) wrote: > > So what is the ceiling on 32-bit processors for RAM? Most of the > > 64-bit vendors are pushing Athalon64 and G5 as "breaking the 4GB > > barrier", and even I can do the math on 2^32. All these 64-bit > > vendors, then, are talking about the limit on ram *per application* > > and not per machine? > > I have been seeing ia-32 servers with 8GB of RAM; it looks as though > there are ways of having them support ("physically, in theory, if you > could get a suitable motherboard") as much as 64GB. > > But that certainly doesn't get you past 2^32 bytes per process, and > possibly not past 2^31 bytes/process. > > >From Linux kernel help: > > CONFIG_NOHIGHMEM: > > Linux can use up to 64 Gigabytes of physical memory on x86 > systems. However, the address space of 32-bit x86 processors is > only 4 Gigabytes large. That means that, if you have a large > amount of physical memory, not all of it can be "permanently > mapped" by the kernel. The physical memory that's not permanently > mapped is called "high memory". > > And that leaves open the question of how much shared memory you can > address. That presumably has to fit into the 4GB, and if your > PostgreSQL processes had (by some fluke) 4GB of shared memory, there > wouldn't be any "local" memory for sort memory and the likes. > > Add to that the consideration that there are reports of Linux "falling > over" when you get to right around 2GB/4GB. I ran a torture test a > while back that _looked_ like it was running into that; I can't verify > that, unfortunately. Well thank goodness that Linux & Postgres work so well on Alpha and long-mode AMD64. -- ----------------------------------------------------------------- Ron Johnson, Jr. ron.l.johnson@cox.net Jefferson, LA USA "Fear the Penguin!!"