| From: | "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Greg Stark" <gsstark(at)mit(dot)edu>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Experimental patch for inter-page delay in VACUUM |
| Date: | 2003-11-10 17:42:44 |
| Message-ID: | 46C15C39FEB2C44BA555E356FBCD6FA4962060@m0114.s-mxs.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > One problem with O_SYNC would be, that the OS does not group writes any
> > more. So the code would need to eighter do it's own sorting and grouping
> > (256k) or use aio, or you won't be able to get the maximum out of the disks.
>
> Or just run multiple writer processes, which I believe is Oracle's
> solution.
That does not help, since for O_SYNC the OS'es (those I know) do not group those
writes together. Oracle allows more than one writer to busy more than one disk(subsystem) and circumvent other per process limitations (mainly on platforms without AIO).
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Larry Rosenman | 2003-11-10 17:57:35 | Re: Experimental patch for inter-page delay in VACUUM |
| Previous Message | Alvaro Herrera | 2003-11-10 17:05:31 | Re: [HACKERS] BEGIN vs START TRANSACTION |