Re: Multiple Indexing, performance impact - Mailing list pgsql-general

From Bruce Momjian
Subject Re: Multiple Indexing, performance impact
Date
Msg-id 200106222156.f5MLuHW26081@candle.pha.pa.us
Whole thread Raw
In response to Multiple Indexing, performance impact  (Daniel Åkerud <zilch@home.se>)
Responses Re: Multiple Indexing, performance impact  (Lincoln Yeoh <lyeoh@pop.jaring.my>)
List pgsql-general
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > Strange that even at 1024 performance still drops off at 7.  Seems it
> > may be more than buffer thrashing.
>
> Yeah, if anything the knee in the curve seems to be worse at 1024
> buffers.  Curious.  Deserves more investigation, perhaps.
>
> This does remind me that I'd been thinking of suggesting that we
> raise the default -B to something more reasonable, maybe 1000 or so
> (yielding an 8-meg-plus shared memory area).  This wouldn't prevent
> people from setting it small if they have a small SHMMAX, but it's
> probably time to stop letting that case drive our default setting.
> Since 64 is already too much to let 7.1 fit in SHMMAX = 1MB, I think
> the original rationale for using 64 is looking pretty broken anyway.
> Comments?

BSD/OS has a 4MB max but we document how to increase it by recompiling
the kernel.  Maybe if we fail the startup we can tell them how to
decrease the buffers in postgresql.conf file.  Seems quite clear.

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

pgsql-general by date:

Previous
From: "Thalis A. Kalfigopoulos"
Date:
Subject: no comment
Next
From: Tom Lane
Date:
Subject: Re: Multiple Indexing, performance impact