Messages in this thread | | | Date | Mon, 29 Jun 2009 23:02:06 +0200 | From | Ingo Molnar <> | Subject | Re: [numbers] perfmon/pfmon overhead of 17%-94% |
| |
* Vince Weaver <vince@deater.net> wrote:
>> If the 5 thousand cycles measurement overhead _still_ matters to >> you under such circumstances then by all means please submit the >> patches to improve it. Despite your claims this is totally >> fixable with the current perfcounters design, Peter outlined the >> steps of how to solve it, you can utilize ptrace if you want to. > > Is it really "totally" fixible? I don't just mean getting the > overhead from ~3000 down to ~100, I mean down to zero.
The thing is, not even pfmon gets it down to zero:
pfmon -e INSTRUCTIONS_RETIRED --follow-fork --aggregate-results ~/million 1000001 INSTRUCTIONS_RETIRED
So ... do you take the hardliner purist view and consider it crap due to that imprecision, or do you take the pragmatist view of also considering the relative relevance of any imperfection? ;-)
Ingo
| |