Re: [SPAM?] Re: Asynchronous I/O Support

From: "Zeugswetter Andreas ADI SD" <ZeugswetterA(at)spardat(dot)at>
To: <mark(at)mark(dot)mielke(dot)cc>
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-23 07:59:30
Message-ID: E1539E0ED7043848906A8FF995BDA57901726499@m0143.s-mxs.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> > 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.

IIRC the configuration of that test was not suitable to show any
benefit.
Minimum requirements to show improvement are:
- very few active sessions (typically less than number of disks)
- a table that spans multiple disks (typically on a stripe set)
(or one intelligent scsi disk)
- only random disk access plans

> You have PostgreSQL on Windows with EMC with async I/O
> support to test with?

No, sorry. Was a MaxDB issue.

Andreas

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Albe Laurenz 2006-10-23 08:00:23 Re: bug or feature, || -operator and NULLs
Previous Message Zeugswetter Andreas ADI SD 2006-10-23 07:47:14 Re: [SPAM?] Re: Asynchronous I/O Support