On Sat, Oct 06, 2007 at 12:30:43PM -0400, George Nychis wrote: > Hey all, > > I'm a bit new to profiling, I've used gprof in the past but this is my > first time using oprofile. I'm running oprofile on the inband code to > try and better understand the m-block performance problem we are seeing. > Since Eric and I's first short attempt at profiling a while ago showed > significant time in the kernel, I've enabled full kernel profiling. > > I haven't specified any specific oprofile options, just sort of started > the daemon, dumped before running the program, ran it for ~1 minute and > saved a session, then examined the single application.
Uhh, you want to reset before running your test case, not dump. Then run the test app for about a minute, then dump and stop. Then opreport -l > I've hosted the results to spare the list some traffic: > http://www.andrew.cmu.edu/user/gnychis/inband_profile_4 > > So it looks like there is a lot of time spent scheduling the threads in > the kernel. We're not concerned about optimizing the application itself. Thanks. If you get a chance, please try again, running oprofile as suggested above. Eric _______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
