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

From Fabio Pardi
Subject Re: Why could different data in a table be processed with differentperformance?
Date
Msg-id 4f53b25c-d1c7-9d6c-c960-bfe81397fa36@portavita.eu
Whole thread Raw
In response to Re: Why could different data in a table be processed with different performance?  (Vladimir Ryabtsev <greatvovan@gmail.com>)
List pgsql-performance

On 09/21/2018 08:28 AM, Vladimir Ryabtsev wrote:

>> but you say you observe a difference even after dropping the cache.
> No, I say I see NO significant difference (accurate to measurement
> error) between "with caches" and after dropping caches. And this is
> explainable, I think. Since I read consequently almost all data from the
> huge table, no cache can fit this data, thus it cannot influence
> significantly on results. And whilst the PK index *could* be cached (in
> theory) I think its data is being displaced from buffers by bulkier
> JSONB data.
> 
> Vlad

I think this is not accurate. If you fetch from an index, then only the
blocks containing the matching records are red from disk and therefore
cached in RAM.

regards,

fabio pardi


pgsql-performance by date:

Previous
From: Fabio Pardi
Date:
Subject: Re: Why could different data in a table be processed with differentperformance?
Next
From: Patrick Molgaard
Date:
Subject: Re: Multi-second pauses blocking even trivial activity