Re: [Discuss-gnuradio] Profiling GNU Radio flow graphs

[Felix Wunsch]

Hi,

using oprofile is quite easy. Basically you configure your profiler, start it, start your application, kill it after some time, kill the profiler and look at the results. You don't have to set any special compiler flags. However, if you want to get annotated source, you need to compile with debug symbols. All this can be done in a simple shell script what makes it very convenient.

For more details I'd like to refer you to the oprofile manual [1] as it's good to read and not too extensive.

In my case, most CPU time is used by memmove (about 40%!). Unfortunately, I wasn't able to figure out where it gets called from.

Best regards,
Felix

[1] http://oprofile.sourceforge.net/doc/index.html


Am 24.08.2012 08:28, schrieb Qing Yang:

Hi Felix,

Currently I also need to profile and optimize my system. Now I just add some some sentences to print the processing time of each block, but this is definitely not a good method. Could you describe your profiling method in more details, perhaps your results can be a reference for me.

Hi Tim,

Have you tried this Kcachegrind on GNU Radio flow graphs? Does it works well? I want to see the profile of each gr module (in python).

--

Yang, Qing

Information Engineering, CUHK

2012/8/24 <address@hidden>

Hi all,

I am currently trying to optimize the performance of my DRM transmitter
and for this purpose I want to profile my flow graphs.

After some googling and searching the archives I stumbled upon oprofile
which looks quite nice to me. However, a first try did not really provide
very significant results. But that could also be due to misconfiguration,
I did not read the manual very carefully...

Just wanted to know if there are other/better solutions for profiling you
would recommend. Any comments are appreciated!

Best regards,
Felix


_______________________________________________
Discuss-gnuradio mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio