pg.ddx.io pgsql-performance@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: Craig Ringer <craig@postnewspapers.com.au>
Cc: pgsql-performance@postgresql.org
Subject: Re: [PERFORMANCE] expanding to SAN: which portion best to move
Date: Tue, 17 May 2011 17:47:09 +0800
Message-ID: <4DD2441D.8040500@postnewspapers.com.au> (raw)
In-Reply-To: <BANLkTin+fqFBktSG9c=XJ=rAOi2K-H9eVA@mail.gmail.com>
References: <BANLkTimDjFDy8Q8vfDVZ4LBKXb1EjVsh4w@mail.gmail.com>
<4DC0D968.3030106@krogh.cc>
<BANLkTi=eNeQmYLqNm-E36G9UPwTnsTtHBw@mail.gmail.com>
<4DC0E525.4060108@krogh.cc>
<BANLkTikg=2SMu5eSBNfW_K8fCXBhZk0Hog@mail.gmail.com>
<BANLkTi=Oo4jRHpBY_74nJrcryr=BLDZR9A@mail.gmail.com>
<BANLkTindOvBQphvGrc-PtxKDNAHkCemssw@mail.gmail.com>
<BANLkTin6CbjJWq=F6=Of=edUnEXLPB94kA@mail.gmail.com>
<BANLkTin+fqFBktSG9c=XJ=rAOi2K-H9eVA@mail.gmail.com>
On 05/17/2011 03:00 PM, Robert Klemme wrote:
> The main point is that you do not benefit from the larger IO bandwidth
> if access patterns do not permit parallel access to both disks (e.g.
> because you first need to read index blocks in order to know the table
> blocks to read).
This makes me wonder if Pg attempts to pre-fetch blocks of interest for
areas where I/O needs can be known in advance, while there's still other
works or other I/O to do. For example, pre-fetching for the next
iteration of a nested loop while still executing the prior one. Is it
even possible?
I'm guessing not, because (AFAIK) Pg uses only synchronous blocking I/O,
and with that there isn't really a way to pre-fetch w/o threads or
helper processes. Linux (at least) supports buffered async I/O, so it'd
be possible to submit such prefetch requests ... on modern Linux
kernels. Portably doing so, though - not so much.
--
Craig Ringer
view thread (17+ messages) latest in thread
Message-ID: <4DD2441D.8040500@postnewspapers.com.au> Permalink: ../4DD2441D.8040500@postnewspapers.com.au/ Also on: postgresql.org/message-id/4DD2441D.8040500@postnewspapers.com.au ·
reply
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Reply to all the recipients using the --to and --cc options: reply via email To: pgsql-performance@postgresql.org Cc: craig@postnewspapers.com.au Subject: Re: [PERFORMANCE] expanding to SAN: which portion best to move In-Reply-To: <4DD2441D.8040500@postnewspapers.com.au> * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox