From: | torikoshia <torikoshia(at)oss(dot)nttdata(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: RFC: Allow EXPLAIN to Output Page Fault Information |
Date: | 2024-12-26 04:15:59 |
Message-ID: | 6023c8ac6b1823e2126a001f668ef245@oss.nttdata.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2024-12-25 00:52, Tom Lane wrote:
> torikoshia <torikoshia(at)oss(dot)nttdata(dot)com> writes:
>> I have attached a PoC patch that modifies EXPLAIN to include page
>> fault
>> information during both the planning and execution phases of a query.
>
> Surely these numbers would be too unstable to be worth anything.
Thanks for your comment!
Hmm, I didn't know these are unstable. If there are any reasons, I'd
like to know about them.
I would like to explore alternative methods for measuring resource
usage, but
I am not aware of other approaches.
(IIUC pg_stat_kcache[1], which is said to provide information about
filesystem layer I/O usage also gets metrics from getrusage(2))
[1] https://github.com/powa-team/pg_stat_kcache
--
Regards,
--
Atsushi Torikoshi
Seconded from NTT DATA GROUP CORPORATION to SRA OSS K.K.
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2024-12-26 05:34:48 | Re: An improvement of ProcessTwoPhaseBuffer logic |
Previous Message | Umar Hayat | 2024-12-26 04:15:36 | Re: Add XMLNamespaces to XMLElement |