Re: Working on huge RAM based datasets

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Andy Ballingall <andy_ballingall(at)bigfoot(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Working on huge RAM based datasets
Date: 2004-07-09 01:41:50
Message-ID: 40EDF7DE.8080900@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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?

Because the PostgreSQL buffer management algorithms are pitiful compared
to Linux's. In 7.5, it's improved with the new ARC algorithm, but still
- the Linux disk buffer cache will be very fast.

Chris

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Andy Ballingall 2004-07-09 09:28:24 Re: Working on huge RAM based datasets
Previous Message Mark Kirkwood 2004-07-09 00:14:32 Re: Terrible performance after deleting/recreating indexes