From: | Ben Chobot <bench(at)silentmedia(dot)com> |
---|---|
To: | Bobby Mozumder <bmozumder(at)gmail(dot)com> |
Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Possible to find disk IOs for a Query? |
Date: | 2016-08-31 22:10:10 |
Message-ID: | EAE112EC-6D0E-412E-A957-15AA4ED43477@silentmedia.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Aug 31, 2016, at 3:01 PM, Bobby Mozumder <bmozumder(at)gmail(dot)com> wrote:
>
> Is it possible to find the number of disk IOs performed for a query? EXPLAIN ANALYZE looks like it shows number of sequential rows scanned, but not number of IOs.
Postgres knows the number of rows it will need to pull to do your query, but it has no way of knowing if a block not in its own cache can be satisfied via filesystem cache, or if it will fall through to disk read. If you are on linux, you might be able to tell the effectiveness of your filesystem cache via something like http://www.brendangregg.com/blog/2014-12-31/linux-page-cache-hit-ratio.html <http://www.brendangregg.com/blog/2014-12-31/linux-page-cache-hit-ratio.html>
…but that's hardly going to show you something as granular as a per-query cost.
From | Date | Subject | |
---|---|---|---|
Next Message | Lukas Fittl | 2016-08-31 22:17:27 | Re: Possible to find disk IOs for a Query? |
Previous Message | Bobby Mozumder | 2016-08-31 22:01:19 | Possible to find disk IOs for a Query? |