From: | Jeremy Harris <jgh(at)wizmail(dot)org> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: CPU bound |
Date: | 2010-12-20 17:59:42 |
Message-ID: | 4D0F998E.7060007@wizmail.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On 2010-12-20 15:48, Kenneth Marshall wrote:
>> And how exactly, given that the kernel does not know whether the CPU is
>> active or waiting on ram, could an application do so?
>>
>
> Exactly. I have only seen this data from hardware emulators. It would
> be nice to have... :)
There's no reason that the cpu hardware couldn't gather such, and
IMHO it's be dead useful, at least at the outermost cache level
(preferably separately at each level). But people have trouble
understanding vmstat already....
Note that dtrace *can* get to the cpu performance counters,
just that the kernel doesn't routinely account for all that info
per-process as routine. I'd expect IBM to have equivalent
facilities.
--
Jeremy
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2010-12-20 18:19:59 | Re: postgres performance tunning |
Previous Message | Greg Smith | 2010-12-20 17:49:16 | Re: postgres performance tunning |