Re: Why could different data in a table be processed with different performance? - Mailing list pgsql-performance

From Vladimir Ryabtsev
Subject Re: Why could different data in a table be processed with different performance?
Date
Msg-id CAMqTPqn=N--+MOr81-5qXvt3zpib-1TURmLjn27eHYj6b6L-qw@mail.gmail.com
Whole thread Raw
In response to Re: Why could different data in a table be processed with differentperformance?  (Justin Pryzby <pryzby@telsasoft.com>)
List pgsql-performance
> did you try either 1) forcing a bitmap scan (of only one index), to force the heap reads to be ordered, if not sequential?  SET enable_indexscan=off (and maybe SET enable_seqscan=off and others as needed).
Disabling index scan made it bitmap.
It is surprising, but this increased read speed in both ranges.
It came two times for "fast" range and 3 times faster for "slow" range (for certain segments of data I checked on, the whole experiment takes a while though).
But there is still a difference between the ranges, it became now ~20 MB/s vs ~6 MB/s.

Vlad

pgsql-performance by date:

Previous
From: Vladimir Ryabtsev
Date:
Subject: Re: Why could different data in a table be processed with different performance?
Next
From: Justin Pryzby
Date:
Subject: Re: Why could different data in a table be processed with differentperformance?