On 06/01/2010 02:59 PM, Steven Rostedt wrote:
One concern is performance. Traces tend to be long, and running python
code on each line will be slow.
If trace-cmd integrates a pager and a search mechanism that looks at the
binary data instead of the text, we could format only the lines that are
displayed. But that is going to be a lot of work and I don't think it's
worth the effort.
Every event gets its own ID. The plugin registers a callback to that ID.
When the ID is hit, the plugin is executed on that event to display its
binary format.
This is done after the data has been saved in binary format to a file.
It may slow down the executing of reading a data file, but it does not
affect the running of the trace one bit.
I meant that viewing would be slowed down. It's an important part of
using ftrace!
How long does the Python formatter take to process 100k or 1M events?
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
