Re: Benchmarks of kernel tracing options (ftrace, ktrace, lttng and perf)

[Michael Rubin]

On Thu, Oct 28, 2010 at 12:27 PM, Mathieu Desnoyers
<mathieu.desnoyers@xxxxxxxxxxxx> wrote:
> * David Sharp (dhsharp@xxxxxxxxxx) wrote:
> Hrm, not quite fair actually. LTTng enables a thread flag that causes
> syscall_trace to be called on sycall entry/exit by default. Please try with the
> following patch to remove the extra syscall overhead.

We started this thread is an attempt to get the ball rolling on
keeping track of these metrics. They seem important for both Google
and Linux as a whole. We published all our work and benchmarks with
hopes that the owners could comment and also run the tests themselves.

Matthieu it might make more sense for you to find the" fair" setup and
publish that, than take the extra time to go back and forth with
David. Once you have the config that best represents what users will
see and you have numbers to go with it, we can then run it in our
environment. I worry you will be forced to send us patch and patch and
patch and we won't have the resources to do a good job in responding
to them. Which is not fair to you.

mrubin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/