| From: | "Zeugswetter Andreas ADI SD" <ZeugswetterA(at)spardat(dot)at> |
|---|---|
| To: | "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Configuring BLCKSZ and XLOGSEGSZ (in 8.3) |
| Date: | 2006-11-28 12:04:18 |
| Message-ID: | E1539E0ED7043848906A8FF995BDA579018FE16D@m0143.s-mxs.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
> I don't doubt that there may be a positive effect from increasing the
> block size. But we haven't seen any analysis of why that
> might be. If it's just to use the disk system bandwith better, maybe
we should
> combine page writes instead or something.
It is usually the reads that need aid. Writes are fast on modern
disksystems since they are
cached.
I think the main effect is reduced OS overhead for the readahead
prediction logic and
reduced system call overhead.
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Meskes | 2006-11-28 12:44:28 | Re: ecpg_config.h not installed |
| Previous Message | Zeugswetter Andreas ADI SD | 2006-11-28 11:58:55 | Re: Potential to_char localization bug |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Sullivan | 2006-11-28 16:40:39 | Re: Configuring BLCKSZ and XLOGSEGSZ (in 8.3) |
| Previous Message | Simon Riggs | 2006-11-28 09:22:37 | Re: Configuring BLCKSZ and XLOGSEGSZ (in 8.3) |