Skip site navigation (1) Skip section navigation (2)

Re: Postgres server crash

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: "Craig A(dot) James" <cjames(at)modgraph-usa(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org, mstone+postgres(at)mathom(dot)us
Subject: Re: Postgres server crash
Date: 2006-11-20 01:59:52
Message-ID: 20061120015952.GA10935@wolff.to (view raw or flat)
Thread:
Lists: pgsql-performance
On Sun, Nov 19, 2006 at 14:12:01 -0800,
  "Craig A. James" <cjames(at)modgraph-usa(dot)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.

In response to

Responses

pgsql-performance by date

Next:From: Craig A. JamesDate: 2006-11-20 06:42:07
Subject: Re: Postgres server crash
Previous:From: Craig A. JamesDate: 2006-11-20 01:00:23
Subject: Re: Postgres server crash

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group