Re: effective_io_concurrency increasing

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Patrick B <patrickbakerbr(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: effective_io_concurrency increasing
Date: 2017-06-19 22:21:20
Message-ID: CAH2-Wzmv371Eib7Z7HnKb9PGUriVfWS=0h6qjtxKgCpHbLBp8A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Jun 19, 2017 at 8:36 AM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> Unfortunately, it is only implemented in very narrow circumstances. You
> have to be doing bitmap index scans of many widely scattered rows to make it
> useful. I don't think that this is all that common of a situation. The
> problem is that at every point in the scan, it has to be possible to know
> what data block it is going to want N iterations in the future, so you can
> inform the kernel to pre-fetch it. That is only easy to know for bitmap
> scans.

I think that you could prefetch in index scans by using the
pointers/downlinks in the immediate parent page of the leaf page that
the index scan currently pins. The sibling pointer in the leaf itself
is no good for this, because there is only one block to prefetch
available at a time.

I think that this is the way index scan prefetch is normally
implemented. Index scans will on average have a much more random
access pattern than what is typical for bitmap heap scans, making this
optimization more compelling, so hopefully someone will get around to
this.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alvaro Herrera 2017-06-19 22:25:21 Re: effective_io_concurrency increasing
Previous Message Merlin Moncure 2017-06-19 22:15:42 Re: performance considerations of jsonb vs separate rows