Re: Why could different data in a table be processed with different performance?

From: Fabio Pardi <f(dot)pardi(at)portavita(dot)eu>
To: pgsql-performance(at)lists(dot)postgresql(dot)org
Subject: Re: Why could different data in a table be processed with different performance?
Date: 2018-09-21 13:12:58
Message-ID: 4f53b25c-d1c7-9d6c-c960-bfe81397fa36@portavita.eu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Patrick Molgaard 2018-09-21 19:07:07 Re: Multi-second pauses blocking even trivial activity
Previous Message Fabio Pardi 2018-09-21 13:08:53 Re: Why could different data in a table be processed with different performance?