Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane writes:
>> 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).
> On Modern(tm) systems, 8 MB is just as arbit
Bruce Momjian <[EMAIL PROTECTED]> writes:
>> We could offer a --with switch to manually choose the default, too.
> Good idea, yes. Not sure if we need a --with switch because they can
> just edit the postgresql.conf or postgresql.conf.sample file.
Well, we have a --with switch for DEF_MAXBACKEN
Tried with 2048 also, it complete took away the strange steep after 7:
D is now 2048
1.A: 36B: 32C: 35D: 31
2.A: 69B: 53C: 38D: 38
3.A: 97B: 79C: 40D: 40
4.A: 131B: 98C: 48D: 43
5.A: 163B: 124C: 52D: 49
6.A: 210
Bruce Momjian <[EMAIL PROTECTED]> writes:
>> Hmm. Anyone like the idea of a platform-specific default established
>> by configure? We could set it in the template file on platforms where
>> the default SHMMAX is too small to allow 1000 buffers.
> Template file seems like a good idea for platfor
Bruce Momjian <[EMAIL PROTECTED]> 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 t
Bruce Momjian <[EMAIL PROTECTED]> writes:
>> 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).
> BSD/OS has a 4MB max but we document how to increase it by recompi
Holy ultra-violet-active macaronies :)
First I changed it to 256, then I changed it to 1024.
-B 128 is A
-B 256 is B
-B 1024 is C
New multiple-index performance data):
1.A: 36B: 32C: 35
2.A: 69B: 53C: 38
3.A: 97B: 79C: 40
4.A: 131B: 98C: 48
5.
