From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | scrappy(at)hub(dot)org (The Hermit Hacker) |
Cc: | abrams(at)philos(dot)umass(dot)edu, hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] include/config.h FOLLOWUP |
Date: | 1998-01-04 19:05:32 |
Message-ID: | 199801041905.OAA04251@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> No, don't make it a run-time or auto-detect thing, just a compile time
> option. By default, leave it at 8192, since "that's the way its always been"...
> but if we are justifying it based on disk block size, its 2x the disk block
> size that my system is setup for. What's the difference between that and making
> it 3x or 4x? Or, hell, would I get a performance increase if I brought it
> down to 4096, which is what my actually disk block size is?
>
> So, what we would really be doing is setting the default to 8192, but give
> the installer the opportunity (with a caveat that this value should be a multiple
> of default file system block size for optimal performance) to increase it as they
> see fit.
I assume you changed the default, becuase the BSD44 default is 8k
blocks, with 1k fragments.
I don't think there is any 'performance' improvement with making it
greater than the file system block size.
--
Bruce Momjian
maillist(at)candle(dot)pha(dot)pa(dot)us
From | Date | Subject | |
---|---|---|---|
Next Message | The Hermit Hacker | 1998-01-04 19:31:49 | Re: [HACKERS] include/config.h FOLLOWUP |
Previous Message | The Hermit Hacker | 1998-01-04 18:18:53 | Re: [HACKERS] include/config.h FOLLOWUP |