It was on my list to change the build-types to "debug" (to provide symbols). I can't remember whether I did that or not.
Other than disk space, there's no down-side that I can see....
on Mar 26, 2014, West, Nathan <[email protected]> wrote:
On Tue, Mar 25, 2014 at 2:27 PM, Luke Berndt <[email protected]> wrote:
> Thanks - I am running an quad-core Intel I5 laptop. It is running Ubuntu
> 13.10. I also have it running on a VM on my 8 Core I7 Macbook.
>
> Do you have any pointers or links on using oprofile with gnuradio? I found
> some material on using GR Performance Counters, but I haven't had a chance
> to try.
>
> I am going to working on learning how to profile using the VM. In the
> meantime, I rolled back the bare metal machine so I can keep my site up.
>
> I installed 3.7 using the build-gnuradio script. When I reinstalled 3.6.5,
> also using build-gnuradio, the performance was still high. I am wondering if
> it actually has something to do with libraries being upgraded. I know the
> script upgraded me from Boost 1.49 to 1.53. Are there some other libraries
> that could have a perf impact? ITPP?
>
I'm not sure what release type build-gnuradio is using, but you want
to do a build that preserves symbols. After that the easiest way I
know of to get a quick glance at what's causing performance issues is
to run 'perf top'. Just run your flowgraph then start up perf top and
whatever is hogging CPU will rise to the top of the list
Nathan
_______________________________________________
Discuss-gnuradio mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
_______________________________________________ Discuss-gnuradio mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
