From: Bruno Wolff III <bruno@wolff.to>
To: Craig A. James <cjames@modgraph-usa.com>
Cc: pgsql-performance@postgresql.org
Cc: mstone+postgres@mathom.us
Subject: Re: Postgres server crash
Date: Sun, 19 Nov 2006 19:59:52 -0600
Message-ID: <20061120015952.GA10935@wolff.to> (raw)
In-Reply-To: <4560D6B1.8060306@modgraph-usa.com>
References: <19583.1163700841@sss.pgh.pa.us>
<Pine.LNX.4.33.0611181713170.19262-100000@denzel.in>
<20061119184105.GC2366@mathom.us>
<4560D6B1.8060306@modgraph-usa.com>
On Sun, Nov 19, 2006 at 14:12:01 -0800,
"Craig A. James" <cjames@modgraph-usa.com> wrote:
>
> These were mostly scientific and graphical apps where reliability took a
> back seat to performance and to program complexity. They would allocate
> 100's of GB of swap space rather than taking the time to design proper data
> structures. If the program crashed every week or two, no big deal -- just
> run it again. Overallocating memory is a valuable technique for such
> applications.
I don't think the above applies generally. Programmers need to be aware of
the working set of CPU bound apps. If the program is constantly paging,
the performance is going to be abysmal.
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: bruno@wolff.to, cjames@modgraph-usa.com, mstone+postgres@mathom.us
Subject: Re: Postgres server crash
In-Reply-To: <20061120015952.GA10935@wolff.to>
* 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