Re: [Discuss-gnuradio] Profiling Gnuradio message based blocks

2017-08-15 Thread Marcus Müller
Dear Jeff, from the top of my head: the perf counters count the time a block spends in its work(), how many items were consumed and produced in calls to work(), as well as things as buffer fillage and such. Well, all these things don't apply to message passing, since there's no call to

[Discuss-gnuradio] Profiling Gnuradio message based blocks

2017-08-15 Thread Jeffrey Grasty
Hi, I am trying to profile some message based blocks with performance monitor. The message blocks appear in the gr-perf-monitorx; however, they do not appear in runtime table. This questions asks same thing: https://lists.gnu.org/archive/html/discuss-gnuradio/2017-01/msg00121.html It looks like

Re: [Discuss-gnuradio] Profiling Gnuradio message based blocks

2017-01-15 Thread Jacob Gilbert
Hi Emanuel, This is related to a larger issue in which the controlport interface (used for performance monitoring in addition to other features) is only started for blocks with at least one stream connection. I submitted a PR for this ( https://github.com/gnuradio/gnuradio/pull/1119) which be

[Discuss-gnuradio] Profiling Gnuradio message based blocks

2017-01-13 Thread Emanuel.Staudinger
Hi all, I managed to get Apache thrift up and running and configured by environment to use the control port and performance counters. gr-perf-monitorx works fine and shows me my flowgraph as intended. My flowgraph consists of several streaming based blocks and many purely message based blocks