Horton

Re: BitmapHeapScan streaming read user and prelim refactoring

Robert Haas <robertmhaas@gmail.com>

View thread View on postgr.es
From: Robert Haas <robertmhaas@gmail.com>
To: Melanie Plageman <melanieplageman@gmail.com>
Cc: Tomas Vondra <tomas@vondra.me>, Nazir Bilal Yavuz <byavuz81@gmail.com>, Dilip Kumar <dilipbalaut@gmail.com>, Heikki Linnakangas <hlinnaka@iki.fi>, Thomas Munro <thomas.munro@gmail.com>, Andres Freund <andres@anarazel.de>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2025-02-12T19:08:35Z
Lists: pgsql-hackers 
On Mon, Feb 10, 2025 at 4:41 PM Melanie Plageman
<melanieplageman@gmail.com> wrote:
> I had taken to thinking of it as "queue depth". But I think that's not
> really accurate. Do you know why we set it to 1 as the default? I
> thought it was because the default should be just prefetch one block
> ahead. But if it was meant to be spindles, was it that most people had
> one spindle (I don't really know what a spindle is)?

AFAIK, we're imagining that people are running PostgreSQL on a hard
drive like the one my desktop machine had when I was in college, which
indeed only had one spindle. There were one or possibly several
magnetic platters rotating around a single point. But today, nobody
has that, certainly not on a production machine. For instance if you
are using RAID or LVM you have several drives hooked up together, so
that would be multiple spindles even if all of them were HDDs, but
probably they are all SSDs which don't have spindles anyway. If you
are on a virtual machine you have a slice of the underlying machine's
I/O and whatever that is it's probably something more complicated than
a single spindle.

To be fair, I guess the concept of effective_io_concurrency isn't
completely meaningless if you think about it as the number of
simultaneous I/O requests that can be in flight at a time. But I still
think it's true that it's hard to make any reasonable guess as to how
you should set this value to get good performance. Maybe people who
work as consultants and configure lots of systems have good intuition
here, but anybody else is probably either not going to know about this
parameter or flail around trying to figure out how to set it.

It might be interesting to try some experiments on a real small VM
from some cloud provider and see what value is optimal there these
days. Then we could set the default to that value or perhaps somewhat
more.

-- 
Robert Haas
EDB: http://www.enterprisedb.com

Commits

  1. Fix bitmapheapscan incorrect recheck of NULL tuples

  2. Increase default maintenance_io_concurrency to 16

  3. Separate TBM[Shared|Private]Iterator and TBMIterateResult

  4. Improve read_stream.c advice for dense streams.

  5. Increase default effective_io_concurrency to 16

  6. Delay extraction of TIDBitmap per page offsets

  7. Add lossy indicator to TBMIterateResult

  8. Move BitmapTableScan per-scan setup into a helper

  9. Add and use BitmapHeapScanDescData struct

  10. Fix bitmap table scan crash on iterator release

  11. Bitmap Table Scans use unified TBMIterator

  12. Add common interface for TBMIterators

  13. Make table_scan_bitmap_next_block() async-friendly

  14. Move EXPLAIN counter increment to heapam_scan_bitmap_next_block

  15. Refactor tidstore.c iterator buffering.

  16. BitmapHeapScan: Remove incorrect assert and reset field

  17. Change BitmapAdjustPrefetchIterator to accept BlockNumber

  18. BitmapHeapScan: Use correct recheck flag for skip_fetch

  19. BitmapHeapScan: Push skip_fetch optimization into table AM

  20. BitmapHeapScan: postpone setting can_skip_fetch

  21. BitmapHeapScan: begin scan after bitmap creation

  22. Fix EXPLAIN Bitmap heap scan to count pages with no visible tuples

  23. Remove redundant snapshot copying from parallel leader to workers

  24. Remove some obsolete smgrcloseall() calls.

  25. Remove the "snapshot too old" feature.

  26. Compute XID horizon for page level index vacuum on primary.