| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig A. James | 2006-11-20 06:42:07 | Re: Postgres server crash |
| Previous Message | Craig A. James | 2006-11-20 01:00:23 | Re: Postgres server crash |