From: Josh Berkus <josh@agliodbs.com>
To: scott.marlowe <scott.marlowe@ihs.com>
Cc: Anjan Dave <adave@vantage.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Tuning for mid-size server
Date: Tue, 21 Oct 2003 10:12:15 -0700
Message-ID: <200310211012.15845.josh@agliodbs.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0310211042040.10616-100000@css120.ihs.com>
References: <Pine.LNX.4.33.0310211042040.10616-100000@css120.ihs.com>
Scott,
> Also, if it's a read only environment, RAID5 with n drives equals the
> performance of RAID0 with n-1 drives.
True.
> Josh, you gotta get out more. IA32 has supported >4 gig ram for a long
> time now, and so has the linux kernel. It uses a paging method to do it.
> Individual processes are still limited to ~3 gig on Linux on 32 bit
> hardware though, so the extra mem will almost certainly spend it's time as
> kernel cache.
Not that you'd want a sigle process to grow that large anyway.
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?
This has all been academic to me to date, as the only very-high-ram systems
I've worked with were Sparc or micros.
--
Josh Berkus
Aglio Database Solutions
San Francisco
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: josh@agliodbs.com, scott.marlowe@ihs.com, adave@vantage.com
Subject: Re: Tuning for mid-size server
In-Reply-To: <200310211012.15845.josh@agliodbs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox