From: Philippe E. <ph...@wa...> - 2003-08-16 14:52:35
|
actually the output is: $ opreport -l vma samples % samples % app name symbol name 0804a5e0 103306 16.8419 529 14.6133 oprofiled opd_put_sample 0804cb00 42776 6.9737 345 9.5304 oprofiled odb_insert we need to add optionnally a field to provide metrics comparison. like: vma samples % samples % %1 - %2 app name symbol name 0804a5e0 103306 16.8419 529 14.6133 (+2.2286) oprofiled opd_put_sample 0804cb00 42776 6.9737 345 9.5304 (-2.5567) oprofiled odb_insert here the metrics is %1 - %0 where %x is the counter number (numbered from left to right). The above example is for two counter but should works for any number of counter. This is for opreport but a similar interface would be used for opdiff. So I think we need a --compare flags to add this field, a --metrics= to allow specifying the metrics (with a default metrics we must choose) and a --sort to change sort order. --compare no parameters, when specified add a field for all counter expect the counter at left in output --metrics="%N / %0" I've already code to implement that, but only a vague idea if it's usefull and how we must specify the user interface Graydon, you worked on something similar through script, any comments ? Especially what do we need to avoid you update your python bindings each time an internal structure of oprofile change ? regards, Phil |