| From: | mark(at)mark(dot)mielke(dot)cc |
|---|---|
| To: | Zeugswetter Andreas ADI SD <ZeugswetterA(at)spardat(dot)at> |
| Cc: | NikhilS <nikkhils(at)gmail(dot)com>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, Mark Kirkwood <markir(at)paradise(dot)net(dot)nz>, Luke Lonergan <llonergan(at)greenplum(dot)com>, Raja Agrawal <raja(dot)agrawal(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [SPAM?] Re: Asynchronous I/O Support |
| Date: | 2006-10-20 17:11:16 |
| Message-ID: | 20061020171116.GA15271@mark.mielke.cc |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Oct 20, 2006 at 05:37:48PM +0200, Zeugswetter Andreas ADI SD wrote:
> Yup, that would be the scenario where it helps (provided that you have
> a smart disk or a disk array and an intelligent OS aio implementation).
> It would be used to fetch the data pages pointed at from an index leaf,
> or the next level index pages.
> We measured the IO bandwidth difference on Windows with EMC as beeing
> nearly proportional to parallel outstanding requests up to at least
Measured it using what? I was under the impression only one
proof-of-implementation existed, and that the scenarios and
configuration of the person who wrote it, did not show significant
improvement.
You have PostgreSQL on Windows with EMC with async I/O support to
test with?
Cheers,
mark
--
mark(at)mielke(dot)cc / markm(at)ncf(dot)ca / markm(at)nortel(dot)com __________________________
. . _ ._ . . .__ . . ._. .__ . . . .__ | Neighbourhood Coder
|\/| |_| |_| |/ |_ |\/| | |_ | |/ |_ |
| | | | | \ | \ |__ . | | .|. |__ |__ | \ |__ | Ottawa, Ontario, Canada
One ring to rule them all, one ring to find them, one ring to bring them all
and in the darkness bind them...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Theo Schlossnagle | 2006-10-20 17:18:04 | xlogdump fixups and WAL log question. |
| Previous Message | Darcy Buskermolen | 2006-10-20 16:32:56 | Re: misbehaving planer? |