Re: Asynchronous I/O Support - Mailing list pgsql-hackers

From NikhilS
Subject Re: Asynchronous I/O Support
Date
Msg-id d3c4af540610172305g4c96c335ub322a55c32491ffb@mail.gmail.com
Whole thread Raw
In response to Re: Asynchronous I/O Support  ("Luke Lonergan" <llonergan@greenplum.com>)
Responses Re: Asynchronous I/O Support  (Mark Kirkwood <markir@paradise.net.nz>)
List pgsql-hackers
Hi,

"bgwriter doing aysncronous I/O for the dirty buffers that it is supposed to sync"
Another decent use-case?

Regards,
Nikhils
EnterpriseDB   http://www.enterprisedb.com

On 10/15/06, Luke Lonergan <llonergan@greenplum.com> wrote:
Martijn,

On 10/15/06 10:56 AM, "Martijn van Oosterhout" <kleptog@svana.org> wrote:

> Have enough systems actually got to the point of actually supporting
> async I/O that it's worth implementing?

I think there are enough high end applications / systems that need it at
this point.

The killer use-case we've identified is for the scattered I/O associated
with index + heap scans in Postgres.  If we can issue ~5-15 I/Os in advance
when the TIDs are widely separated it has the potential to increase the I/O
speed by the number of disks in the tablespace being scanned.  At this
point, that pattern will only use one disk.

- Luke



---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
       subscribe-nomail command to majordomo@postgresql.org so that your
       message can get through to the mailing list cleanly



--
All the world's a stage, and most of us are desperately unrehearsed.

pgsql-hackers by date:

Previous
From: NikhilS
Date:
Subject: Re: Additional stats for Relations
Next
From: Mark Kirkwood
Date:
Subject: Re: Asynchronous I/O Support