Re: Working on huge RAM based datasets - Mailing list pgsql-performance

From Merlin Moncure
Subject Re: Working on huge RAM based datasets
Date
Msg-id 6EE64EF3AB31D5448D0007DD34EEB34101AEC2@Herge.rcsinc.local
Whole thread Raw
In response to Working on huge RAM based datasets  ("Andy Ballingall" <andy_ballingall@bigfoot.com>)
Responses Re: Working on huge RAM based datasets
List pgsql-performance
> What is it about the buffer cache that makes it so unhappy being able
to
> hold everything? I don't want to be seen as a cache hit fascist, but
isn't
> it just better if the data is just *there*, available in the
postmaster's
> address space ready for each backend process to access it, rather than
> expecting the Linux cache mechanism, optimised as it may be, to have
to do
> the caching?

The disk cache on most operating systems is optimized.  Plus, keeping
shared buffers low gives you more room to bump up the sort memory, which
will make your big queries run faster.

Merlin


pgsql-performance by date:

Previous
From: Christopher Kings-Lynne
Date:
Subject: Re: Working on huge RAM based datasets
Next
From: Bill Chandler
Date:
Subject: Re: Terrible performance after deleting/recreating indexes