# Measuring performance of module

**URL:** <https://www.ruby-forum.com/t/measuring-performance-of-module/242291>\
**Category:** GNU Radio\
**Created:** [June 12, 2015, 5:02am UTC](https://www.ruby-forum.com/t/measuring-performance-of-module/242291 "2015-06-12T05:02:37Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![musicdenotation](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/ea666f/32.png) [@musicdenotation](https://www.ruby-forum.com/u/musicdenotation)\
**Post date:** [June 12, 2015, 5:02am UTC](https://www.ruby-forum.com/t/measuring-performance-of-module/242291/1 "2015-06-12T05:02:37Z")

</div>

My OOT module seems to be almost done in implementation.

I am wondering that which and how performance metric can be measured.

I am considering the basic communication performance metrics such as  
throughput, BER/PER vs SNR. And such metrics are rather easy to measure.  
So  
there are not what I have difficulties to measure.

As an SDR platform, I think memory(buffer) usage and processing time per  
block can be importatnt metrics. Thus, the question is… How can I  
measure  
such GNU Radio-related metircs? Should I put codes which calculate  
metrics  
inside each block? Or can it be done in other ways?

Regards,  
Jeon.

---

<div class="post-metadata">

**Author:** ![Jeon](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/e8c25b/32.png) [@Jeon](https://www.ruby-forum.com/u/Jeon)\
**Post date:** [June 12, 2015, 8:25am UTC](https://www.ruby-forum.com/t/measuring-performance-of-module/242291/2 "2015-06-12T08:25:55Z")

</div>

Have a look at the performance counters, and especially the graphical  
monitor, gr-perf-monitorx. It does quite exactly what you describe.

Best regards,  
Marcus

---

<div class="post-metadata">

**Author:** ![Jeon](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/e8c25b/32.png) [@Jeon](https://www.ruby-forum.com/u/Jeon)\
**Post date:** [June 12, 2015, 3:26pm UTC](https://www.ruby-forum.com/t/measuring-performance-of-module/242291/3 "2015-06-12T15:26:34Z")

</div>

On Fri, Jun 12, 2015 at 2:24 AM, Marcus Müller  
[removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
wrote:

> Have a look at the performance counters, and especially the graphical  
> monitor, gr-perf-monitorx. It does quite exactly what you describe.
> 
> Best regards,  
> Marcus

Here’s a paper that I wrote on it:

> **[Second Workshop of Software Radio Implementation Forum (SRIF 2013) - ACM...](http://conferences.sigcomm.org/sigcomm/2013/srif.php)**

And some more inf on the wiki:  
[https://gnuradio.org/redmine/projects/gnuradio/wiki/PerformanceCounters](https://gnuradio.org/redmine/projects/gnuradio/wiki/PerformanceCounters)

Note that to use Performance Monitor, you’ll need the master branch of  
GNU  
Radio after we reintroduced ControlPort:  
[https://gnuradio.org/redmine/projects/gnuradio/wiki/ControlPort](https://gnuradio.org/redmine/projects/gnuradio/wiki/ControlPort)

Tom

---

<div class="post-metadata">

**Author:** ![Jeon](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/e8c25b/32.png) [@Jeon](https://www.ruby-forum.com/u/Jeon)\
**Post date:** [June 15, 2015, 5:42am UTC](https://www.ruby-forum.com/t/measuring-performance-of-module/242291/4 "2015-06-15T05:42:21Z")

</div>

Dear Tom and Marcus

Thank you for very detailed explanations.

Regards,  
Jeon.

2015-06-12 22:24 GMT+09:00 Tom R. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid):